Re: Co-maintainer, a least for some time?

Re: Co-maintainer, a least for some time?

[Thomas Renkert]

What about using launchpad.net for bugtracking?

Bugreports and code reviews can be done via email so they could be cc:ed
to the traditional mailing list while they would show up at the same
time in the web interface.

Also, launchpad encourages more non-programming users to send in and
react on bugs and patches via the "answers"-interface.

By this, maybe at least some of the maintenance tasks can be distributed
more evenly among people who would occasionaly check out a few lines of
code but who don't feel familiar enough with lisp an a large scale.

Just a thought...

Cheers,
Thomas Renkert

Re: Re: Co-maintainer, a least for some time?

[John Wiegley]

On May 20, 2010, at 1:52 PM, Thomas Renkert wrote:

> What about using launchpad.net for bugtracking?

GitHub also has simple issue tracking, with the advantage that it can bind very closely with Git commits.

John

Re: Re: Co-maintainer, a least for some time?

[Greg Newman]

[-- Attachment #1.1: Type: text/plain, Size: 702 bytes --]

I have a mirror of Org up on Bitbucket at
http://bitbucket.org/mirror/org-mode
It wouldn't take much to have Jesper turn on the issues feature for it if
there is interest. (just sayin)

On Thu, May 20, 2010 at 5:34 PM, John Wiegley <jwiegley@gmail.com> wrote:

> On May 20, 2010, at 1:52 PM, Thomas Renkert wrote:
>
> > What about using launchpad.net for bugtracking?
>
> GitHub also has simple issue tracking, with the advantage that it can bind
> very closely with Git commits.
>
> John
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

[-- Attachment #1.2: Type: text/html, Size: 1319 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: Co-maintainer, a least for some time?

[John Wiegley]

[-- Attachment #1.1: Type: text/plain, Size: 383 bytes --]

On May 20, 2010, at 5:57 PM, Greg Newman wrote:

> I have a mirror of Org up on Bitbucket at http://bitbucket.org/mirror/org-mode
> It wouldn't take much to have Jesper turn on the issues feature for it if there is interest. (just sayin)

I have a Git mirror on http://github.com/jwiegley/org-mode (have had for some time), and it's issue tracking feature is already on.

John

[-- Attachment #1.2: Type: text/html, Size: 1270 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: Co-maintainer, a least for some time?

[Greg Newman]

[-- Attachment #1.1: Type: text/plain, Size: 528 bytes --]

wow.  I had no idea John.  Thanks for letting me know!!

On Thu, May 20, 2010 at 6:24 PM, John Wiegley <jwiegley@gmail.com> wrote:

> On May 20, 2010, at 5:57 PM, Greg Newman wrote:
>
> I have a mirror of Org up on Bitbucket at
> http://bitbucket.org/mirror/org-mode
> It wouldn't take much to have Jesper turn on the issues feature for it if
> there is interest. (just sayin)
>
>
> I have a Git mirror on http://github.com/jwiegley/org-mode (have had for
> some time), and it's issue tracking feature is already on.
>
> John
>

[-- Attachment #1.2: Type: text/html, Size: 1350 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Co-maintainer, a least for some time?

[Uday S Reddy]

On 5/20/2010 6:52 PM, Thomas Renkert wrote:
> What about using launchpad.net for bugtracking?
>
> Bugreports and code reviews can be done via email so they could be cc:ed
> to the traditional mailing list while they would show up at the same
> time in the web interface.
>
> Also, launchpad encourages more non-programming users to send in and
> react on bugs and patches via the "answers"-interface.
>
> By this, maybe at least some of the maintenance tasks can be distributed
> more evenly among people who would occasionaly check out a few lines of
> code but who don't feel familiar enough with lisp an a large scale.

Plus 1 for Launchpad.

We use it for maintaining VM and the collection of facilities on the site work quite well.  The main downside is its over-reliance on the web.  The other is that it uses Bazaar for version control, which is probably not as streamlined as Git.

But Launchpad is an integrated project management site that allows you to schedule milestores/releases, allocate bugs/issues to them, and makes sure that everything gets done.  It provides for a variety of roles such as bug supervisor, driver, release manager etc., and allow for bugs/issues to be allocated to various members of the team.  For a large team of contributors, which is what Org mode seems to be tending towards, it could be a big win.

You can check out the VM home page, https://launchpad.net/vm, to see how it works.

Cheers,
Uday

Co-maintainer, a least for some time?

[Carsten Dominik]

Dear all,

I am having a lot of trouble keeping up with everything here in emacs- 
orgmode, in combination with the rest of my life.

Is there anyone who would be willing to step up as a co-maintainer, at  
least for some time?

The tasks would include looking at small patches people submit, making  
decision about whether to apply them, checking copyright issues, and  
applying the patches.  I will be around, so important decisions can be  
deferred to me.

People I know who would be technically able an have enough overview  
over Org include
a couple of obvious choices

Dan
Eric
Bastien
Nick
Bernt
David Maus
John Wiegley
Matt, maybe

I may well have overlooked someone else who could do this as well,  
please do not be offended if I left you off this list.

I completely understand if all of you say no, of course - this is just  
an attempt to keep some control of my life :-)

- Carsten

Re: Co-maintainer, a least for some time?

[Bastien]

Hi Carsten,

Carsten Dominik <carsten.dominik@gmail.com> writes:

> Is there anyone who would be willing to step up as a co-maintainer, at
> least for some time?

I'd be glad to help, but I'm short of time for the moment and I prefer
to concentrate on maintaining the server and Worg.

You made Org a project people would be proud to co-maintain, I'm sure
someone good will step in!

-- 
 Bastien

Re: Co-maintainer, a least for some time?

[Dan Davison]

Bastien <bastien.guerry@wikimedia.fr> writes:

> Hi Carsten,
>
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> Is there anyone who would be willing to step up as a co-maintainer, at
>> least for some time?
>
> I'd be glad to help, but I'm short of time for the moment and I prefer
> to concentrate on maintaining the server and Worg.

I'm afraid I can't devote significantly more time. (In any case, I do
not know the agenda and task/time management side of org well enough.)

But I would be happy to help out in a, err, coalition. Would it be
possible for us to develop a slightly more formalised triage/bug
tracking system whereby any list member who feels able to can say "I'll
look into this and report back with a recommendation for
action". Perhaps this would work via a jointly maintained todo list on
Worg or elsewhere? Any thoughts? Or is this optimistic and do we really
need one person to step up?

Dan


>
> You made Org a project people would be proud to co-maintain, I'm sure
> someone good will step in!

Re: Re: Co-maintainer, a least for some time?

[Eric Schulte]

Hi Carsten,

Dan Davison <davison@stats.ox.ac.uk> writes:

> Bastien <bastien.guerry@wikimedia.fr> writes:
>
>> Hi Carsten,
>>
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>
>>> Is there anyone who would be willing to step up as a co-maintainer, at
>>> least for some time?

I'm sorry to say that I don't have enough time to step up in any real
sustained way.  I've been continually amazed and grateful for the amount
of time you have been able to give to our community.

>>
>> I'd be glad to help, but I'm short of time for the moment and I
>>prefer to concentrate on maintaining the server and Worg.
>
> I'm afraid I can't devote significantly more time. (In any case, I do
> not know the agenda and task/time management side of org well enough.)
>

Likewise, my org expertise is fairly one or two sided, leaving out large
swaths of functionality -- e.g. I have no idea how GTD works.

>
> But I would be happy to help out in a, err, coalition. Would it be
> possible for us to develop a slightly more formalised triage/bug
> tracking system whereby any list member who feels able to can say "I'll
> look into this and report back with a recommendation for
> action".

If this is possible (I know we've talked about an org-mode based bug
tracker before with lukewarm results) then I should be able to help
tackle the stray bug such a model.

On org-babel we've had some success tracking pending development, and
tracking bugs in a single monolithic org-mode file in a github
repository [1].

Best -- Eric

> Perhaps this would work via a jointly maintained todo list on Worg or
> elsewhere? Any thoughts? Or is this optimistic and do we really need
> one person to step up?
>
> Dan
>
>
>>
>> You made Org a project people would be proud to co-maintain, I'm sure
>> someone good will step in!
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Footnotes: 
[1]  http://github.com/eschulte/babel-dev

Re: Re: Co-maintainer, a least for some time?

[Carsten Dominik]

On May 19, 2010, at 4:28 PM, Eric Schulte wrote:

> Hi Carsten,
>
> Dan Davison <davison@stats.ox.ac.uk> writes:
>
>> Bastien <bastien.guerry@wikimedia.fr> writes:
>>
>>> Hi Carsten,
>>>
>>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>>
>>>> Is there anyone who would be willing to step up as a co- 
>>>> maintainer, at
>>>> least for some time?
>
> I'm sorry to say that I don't have enough time to step up in any real
> sustained way.

I do believe that with org-babel, you and Dan *certainly* do your share.

> I've been continually amazed and grateful for the amount
> of time you have been able to give to our community.

In fact, it is more than can really afford - but I am a junkie who  
needs to deal with his problems ...

>
>>>
>>> I'd be glad to help, but I'm short of time for the moment and I
>>> prefer to concentrate on maintaining the server and Worg.
>>
>> I'm afraid I can't devote significantly more time. (In any case, I do
>> not know the agenda and task/time management side of org well  
>> enough.)
>>
>
> Likewise, my org expertise is fairly one or two sided, leaving out  
> large
> swaths of functionality -- e.g. I have no idea how GTD works.
>
>>
>> But I would be happy to help out in a, err, coalition. Would it be
>> possible for us to develop a slightly more formalised triage/bug
>> tracking system whereby any list member who feels able to can say  
>> "I'll
>> look into this and report back with a recommendation for
>> action".
>
> If this is possible (I know we've talked about an org-mode based bug
> tracker before with lukewarm results) then I should be able to help
> tackle the stray bug such a model.
>
> On org-babel we've had some success tracking pending development, and
> tracking bugs in a single monolithic org-mode file in a github
> repository [1].
>
> Best -- Eric
>
>> Perhaps this would work via a jointly maintained todo list on Worg or
>> elsewhere? Any thoughts? Or is this optimistic and do we really need
>> one person to step up?
>>
>> Dan
>>
>>
>>>
>>> You made Org a project people would be proud to co-maintain, I'm  
>>> sure
>>> someone good will step in!
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
> Footnotes:
> [1]  http://github.com/eschulte/babel-dev
>

- Carsten

Re: Co-maintainer, a least for some time?

[Carsten Dominik]

On May 19, 2010, at 3:17 PM, Dan Davison wrote:

> Bastien <bastien.guerry@wikimedia.fr> writes:
>
>> Hi Carsten,
>>
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>
>>> Is there anyone who would be willing to step up as a co- 
>>> maintainer, at
>>> least for some time?
>>
>> I'd be glad to help, but I'm short of time for the moment and I  
>> prefer
>> to concentrate on maintaining the server and Worg.
>
> I'm afraid I can't devote significantly more time. (In any case, I do
> not know the agenda and task/time management side of org well enough.)
>
> But I would be happy to help out in a, err, coalition. Would it be
> possible for us to develop a slightly more formalised triage/bug
> tracking system whereby any list member who feels able to can say  
> "I'll
> look into this and report back with a recommendation for
> action". Perhaps this would work via a jointly maintained todo list on
> Worg or elsewhere? Any thoughts? Or is this optimistic and do we  
> really
> need one person to step up?

I think an issue-tracking system would be great.  And if there are  
other people besides John who want to take up individual issues, I am  
sure this would be good.

I will be happy with anything you propose in this direction.  Also I  
know that John is (I think) tracking ledger issues in org-mode - maybe  
we can use his setup in a file that is part of the git repo?

If we have reports continue to come in on the mailing list, then a bug  
tracker could use the message number on gmane as a reference number.   
So the discussions could stay on the list, but negotiation and  
assignment would happen in the tracker.

But - I have no experience with bug trackers, so anything anyone will  
put forward would be an improvement.

- Carsten

Re: Re: Co-maintainer, a least for some time?

[Karsten Heymann]

Hi,

Am 19.05.2010 17:46, schrieb Carsten Dominik:
> I think an issue-tracking system would be great.  And if there are
> other people besides John who want to take up individual issues, I am
> sure this would be good.

One solution would be to switch the git repository to github.com and use
it's integrates issues functionality. From their site:

  Issues

  GitHub Issues adds lightweight issue tracking tightly integrated with
  your repository. Close issues from commit messages, let users label
  and vote on issues and drag & drop issues to priorize.

See it in action at
http://github.com/splitbrain/dokuwiki-plugin-data/issues

Maybe it's worth a look.

Yours
Karsten

Re: Re: Co-maintainer, a least for some time?

[Matthew Jones]

[-- Attachment #1.1: Type: text/plain, Size: 1513 bytes --]

MobileOrg and MobileOrg Android both use Github, and we both use the issue
tracker.   Another boon to using Github for the project would be benefitting
from individual contributors maintaining "fork"s of the main repository...
then a maintainer could merge in fixes and features that others have worked
on with ease.

I have had several folks contribute to MobileOrg for Android in just this
manner and as the maintainer it has made my life very easy.

73,
Matthew W. Jones (KI4ZIB)
http://matburt.net


On Wed, May 19, 2010 at 2:08 PM, Karsten Heymann <kheymann@blue-cable.net>wrote:

> Hi,
>
> Am 19.05.2010 17:46, schrieb Carsten Dominik:
> > I think an issue-tracking system would be great.  And if there are
> > other people besides John who want to take up individual issues, I am
> > sure this would be good.
>
> One solution would be to switch the git repository to github.com and use
> it's integrates issues functionality. From their site:
>
>  Issues
>
>  GitHub Issues adds lightweight issue tracking tightly integrated with
>  your repository. Close issues from commit messages, let users label
>  and vote on issues and drag & drop issues to priorize.
>
> See it in action at
> http://github.com/splitbrain/dokuwiki-plugin-data/issues
>
> Maybe it's worth a look.
>
> Yours
> Karsten
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

[-- Attachment #1.2: Type: text/html, Size: 2312 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: Co-maintainer, a least for some time?

[Anthony Lander]

On 10-May-19, at 2:08 PM, Karsten Heymann wrote:

> Hi,
>
> Am 19.05.2010 17:46, schrieb Carsten Dominik:
>> I think an issue-tracking system would be great.  And if there are
>> other people besides John who want to take up individual issues, I am
>> sure this would be good.
>
> One solution would be to switch the git repository to github.com and  
> use
> it's integrates issues functionality.


+1

That would make it possible for people like me to cherry-pick issues  
to work on, and leave Carsten & other people to approve and commit  
patches rather than make them.

   -anthony

Re: Re: Co-maintainer, a least for some time?

[Carsten Dominik]

On May 19, 2010, at 8:51 PM, Anthony Lander wrote:

>
> On 10-May-19, at 2:08 PM, Karsten Heymann wrote:
>
>> Hi,
>>
>> Am 19.05.2010 17:46, schrieb Carsten Dominik:
>>> I think an issue-tracking system would be great.  And if there are
>>> other people besides John who want to take up individual issues, I  
>>> am
>>> sure this would be good.
>>
>> One solution would be to switch the git repository to github.com  
>> and use
>> it's integrates issues functionality.
>
>
> +1
>
> That would make it possible for people like me to cherry-pick issues  
> to work on, and leave Carsten & other people to approve and commit  
> patches rather than make them.

Why is that easier on GitHub than on any web-based git hosting system
(it may well be - only I don't know!)

- Carsten

Re: Re: Co-maintainer, a least for some time?

[Anthony Lander]

On 10-May-19, at 5:23 PM, Carsten Dominik wrote:

>
> On May 19, 2010, at 8:51 PM, Anthony Lander wrote:
>
>>
>> On 10-May-19, at 2:08 PM, Karsten Heymann wrote:
>>
>>> Hi,
>>>
>>> Am 19.05.2010 17:46, schrieb Carsten Dominik:
>>>> I think an issue-tracking system would be great.  And if there are
>>>> other people besides John who want to take up individual issues,  
>>>> I am
>>>> sure this would be good.
>>>
>>> One solution would be to switch the git repository to github.com  
>>> and use
>>> it's integrates issues functionality.
>>
>>
>> +1
>>
>> That would make it possible for people like me to cherry-pick  
>> issues to work on, and leave Carsten & other people to approve and  
>> commit patches rather than make them.
>
> Why is that easier on GitHub than on any web-based git hosting system
> (it may well be - only I don't know!)

I don't know that it matters. I am just familiar with github.

Re: Re: Co-maintainer, a least for some time?

[Carsten Dominik]

On May 19, 2010, at 8:08 PM, Karsten Heymann wrote:

> Hi,
>
> Am 19.05.2010 17:46, schrieb Carsten Dominik:
>> I think an issue-tracking system would be great.  And if there are
>> other people besides John who want to take up individual issues, I am
>> sure this would be good.
>
> One solution would be to switch the git repository to github.com and  
> use
> it's integrates issues functionality. From their site:
>
>  Issues
>
>  GitHub Issues adds lightweight issue tracking tightly integrated with
>  your repository. Close issues from commit messages, let users label
>  and vote on issues and drag & drop issues to priorize.

That might be interesting.  I just got a mail from John, he will set  
up patchwork for us, which seems to be an automated issue-tracking  
system based on patches on a mailing list.  This looks good to me  
because it keeps thinks on the mailing list which has worked for us so  
far.  Lets start with that, and think about moving to github for a bit  
longer.

- Carsten

>
> See it in action at
> http://github.com/splitbrain/dokuwiki-plugin-data/issues
>
> Maybe it's worth a look.
>
> Yours
> Karsten
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

- Carsten

Re: Re: Co-maintainer, a least for some time?

[Nick Dokos]

Carsten Dominik <carsten.dominik@gmail.com> wrote:

> 
> That might be interesting.  I just got a mail from John, he will set
> up patchwork for us, which seems to be an automated issue-tracking
> system based on patches on a mailing list.  This looks good to me
> because it keeps thinks on the mailing list which has worked for us so
> far.  Lets start with that, and think about moving to github for a bit
> longer.
> 

AFAIK, patchwork (http://ozlabs.org/~jk/projects/patchwork/) snags
*patches* off the mailing list and squirrels them away so they are
not lost, but it is not an issue-tracking system.

Nick