I opened a bug a while ago to be able to push HTML files via bzr to a
conventional branch name and be able to see these files served
statically by launchpad on a conventional URL on my launchpad project.
My bug was marked as a duplicate of this wiki bug, even though the
under-the-hood, the edition workflow, ressource usage and audience for
such a feature is very different than a Wiki application. One of the
main difference of my feature request is that I do not really want or
need to edit files via the browser, I am fine with my local text
editor.
The feature I describe is closely inspired from the <login>.github.com branch.
Now Github has came up with a feature which makes it super easy for
people to edit a file via the browser, github takes care of creating a
fork of the project and sends a pull request of your changes to the
owner of the file you edited.
With Github, you can do both:
1. powerful local edit with vi/emacs,
2. simple through the browser edit
Keep up the good work on Launchpad,
Cheers
On Mon, May 30, 2011 at 7:59 AM, Robert Collins
<email address hidden> wrote:
> @Geoff - I will on the technical aspects of it ( I'm subscribed to the
> wiki anyhow). jml is going to be unavailable this week so it will need
> to wait for him to return.
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (476472).
> https://bugs.launchpad.net/bugs/240067
>
> Title:
> Launchpad projects need wikis
>
> Status in Launchpad itself:
> In Progress
>
> Bug description:
> Launchpad needs a Wiki unrelated to Ubuntu. When we opened our open
> source project (ubuntu related, in a way) i was uncertain about being
> allowed to use Ubuntu wiki to fill one (1) page about the project.
>
> I really think you should provide a wiki to every project in launchpad
> (maybe with the chance to choose to have an external one).
>
> The rationale is:
> - having an own wiki requires hosting. Why use launchpad for bugtracking and buying hosting space just for the wiki ?
> - Ubuntu wiki is inherently unrelated for many of the projects.
> - Launchpad's blueprints require an external site. This shouldn't be necessary
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/launchpad/+bug/240067/+subscribe
>
Hi,
I opened a bug a while ago to be able to push HTML files via bzr to a
conventional branch name and be able to see these files served
statically by launchpad on a conventional URL on my launchpad project.
My bug was marked as a duplicate of this wiki bug, even though the
under-the-hood, the edition workflow, ressource usage and audience for
such a feature is very different than a Wiki application. One of the
main difference of my feature request is that I do not really want or
need to edit files via the browser, I am fine with my local text
editor.
The feature I describe is closely inspired from the <login>.github.com branch.
Now Github has came up with a feature which makes it super easy for
people to edit a file via the browser, github takes care of creating a
fork of the project and sends a pull request of your changes to the
owner of the file you edited.
https:/ /github. com/blog/ 844-forking- with-the- edit-button
With Github, you can do both:
1. powerful local edit with vi/emacs,
2. simple through the browser edit
Keep up the good work on Launchpad,
Cheers
On Mon, May 30, 2011 at 7:59 AM, Robert Collins /bugs.launchpad .net/bugs/ 240067 /bugs.launchpad .net/launchpad/ +bug/240067/ +subscribe
<email address hidden> wrote:
> @Geoff - I will on the technical aspects of it ( I'm subscribed to the
> wiki anyhow). jml is going to be unavailable this week so it will need
> to wait for him to return.
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (476472).
> https:/
>
> Title:
> Launchpad projects need wikis
>
> Status in Launchpad itself:
> In Progress
>
> Bug description:
> Launchpad needs a Wiki unrelated to Ubuntu. When we opened our open
> source project (ubuntu related, in a way) i was uncertain about being
> allowed to use Ubuntu wiki to fill one (1) page about the project.
>
> I really think you should provide a wiki to every project in launchpad
> (maybe with the chance to choose to have an external one).
>
> The rationale is:
> - having an own wiki requires hosting. Why use launchpad for bugtracking and buying hosting space just for the wiki ?
> - Ubuntu wiki is inherently unrelated for many of the projects.
> - Launchpad's blueprints require an external site. This shouldn't be necessary
>
> To unsubscribe from this bug, go to:
> https:/
>