* [sup-devel] Rubymail maintainership
@ 2014-01-28 1:18 Per Andersson
2014-01-28 7:55 ` Gaute Hope
0 siblings, 1 reply; 4+ messages in thread
From: Per Andersson @ 2014-01-28 1:18 UTC (permalink / raw)
To: sup-devel
Hi!
I am the Debian maintainer for sup.
Recently Sup developers adopted ncursesw-ruby (the ncursesw gem) and
became the new upstream for that. (Instead of having a fork.)
Since a few days ago the original upstream now carries the exact same
functionality. Is there any reason for carrying a fork of this any longer?
I understand that the in the future a migration away from rmail is planned.
In the meantime, using rmail gem, could reduce complexity. Perhaps a
similar move as with ncursesw-ruby can be made, adopting active
maintainership? (I can volunteer for this!)
As Matt states, rubymail is looking for active maintainership
https://github.com/matta/rubymail/pull/2#issuecomment-33173575
--
Per
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-devel] Rubymail maintainership
2014-01-28 1:18 [sup-devel] Rubymail maintainership Per Andersson
@ 2014-01-28 7:55 ` Gaute Hope
2014-01-28 21:21 ` Per Andersson
0 siblings, 1 reply; 4+ messages in thread
From: Gaute Hope @ 2014-01-28 7:55 UTC (permalink / raw)
To: sup-devel
[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]
Excerpts from Per Andersson's message of 2014-01-28 02:18:35 +0100:
> Hi!
>
> I am the Debian maintainer for sup.
>
> Recently Sup developers adopted ncursesw-ruby (the ncursesw gem) and
> became the new upstream for that. (Instead of having a fork.)
>
> Since a few days ago the original upstream now carries the exact same
> functionality. Is there any reason for carrying a fork of this any longer?
Where is upstream for this, I'm not sure if I am following you? The only
active fork of ncurses-ruby (ncursesw-ruby) that I can find is ours -
which is now known as 'ncursesw' in gem world (ncursesw-sup has been
removed).
> I understand that the in the future a migration away from rmail is planned.
> In the meantime, using rmail gem, could reduce complexity. Perhaps a
> similar move as with ncursesw-ruby can be made, adopting active
> maintainership? (I can volunteer for this!)
>
> As Matt states, rubymail is looking for active maintainership
>
> https://github.com/matta/rubymail/pull/2#issuecomment-33173575
>
If you are up for it, that would be good, we might as well push directly
to RMail (and drop rmail-sup). I suggest you contact Matt and we migrate
the rmail-sup repoistory in sup-heliotrope (at github) to use the rmail
namespace. If he wants, we could also just move his repository to the
sup-heliotrope organization.
Please also make sure that the other maintainers of sup are
owners of the rmail gem so that it is not all dependant on one person.
Cheers, Gaute
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-devel] Rubymail maintainership
2014-01-28 7:55 ` Gaute Hope
@ 2014-01-28 21:21 ` Per Andersson
2014-01-29 8:59 ` Gaute Hope
0 siblings, 1 reply; 4+ messages in thread
From: Per Andersson @ 2014-01-28 21:21 UTC (permalink / raw)
To: Sup developer discussion
On Tue, Jan 28, 2014 at 8:55 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
> Excerpts from Per Andersson's message of 2014-01-28 02:18:35 +0100:
>> Hi!
>>
>> I am the Debian maintainer for sup.
>>
>> Recently Sup developers adopted ncursesw-ruby (the ncursesw gem) and
>> became the new upstream for that. (Instead of having a fork.)
>>
>> Since a few days ago the original upstream now carries the exact same
>> functionality. Is there any reason for carrying a fork of this any longer?
>
> Where is upstream for this, I'm not sure if I am following you? The only
> active fork of ncurses-ruby (ncursesw-ruby) that I can find is ours -
> which is now known as 'ncursesw' in gem world (ncursesw-sup has been
> removed).
It was late when I wrote this. What I mean, but did not manage to put in
writing, is that the rmail-sup gem carries the same functionality. And my
suggestion was that we adopt active maintainership of rmail.
Sorry for the total confusion, I was tired...
>> I understand that the in the future a migration away from rmail is planned.
>> In the meantime, using rmail gem, could reduce complexity. Perhaps a
>> similar move as with ncursesw-ruby can be made, adopting active
>> maintainership? (I can volunteer for this!)
>>
>> As Matt states, rubymail is looking for active maintainership
>>
>> https://github.com/matta/rubymail/pull/2#issuecomment-33173575
>>
>
> If you are up for it, that would be good, we might as well push directly
> to RMail (and drop rmail-sup). I suggest you contact Matt and we migrate
> the rmail-sup repoistory in sup-heliotrope (at github) to use the rmail
> namespace. If he wants, we could also just move his repository to the
> sup-heliotrope organization.
I'll contact Matt and ask!
> Please also make sure that the other maintainers of sup are
> owners of the rmail gem so that it is not all dependant on one person.
Absolutely!
Best,
Per
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-devel] Rubymail maintainership
2014-01-28 21:21 ` Per Andersson
@ 2014-01-29 8:59 ` Gaute Hope
0 siblings, 0 replies; 4+ messages in thread
From: Gaute Hope @ 2014-01-29 8:59 UTC (permalink / raw)
To: sup-devel
[-- Attachment #1: Type: text/plain, Size: 2278 bytes --]
Excerpts from Per Andersson's message of 2014-01-28 22:21:48 +0100:
> On Tue, Jan 28, 2014 at 8:55 AM, Gaute Hope <eg@gaute.vetsj.com> wrote:
> > Excerpts from Per Andersson's message of 2014-01-28 02:18:35 +0100:
> >> Hi!
> >>
> >> I am the Debian maintainer for sup.
> >>
> >> Recently Sup developers adopted ncursesw-ruby (the ncursesw gem) and
> >> became the new upstream for that. (Instead of having a fork.)
> >>
> >> Since a few days ago the original upstream now carries the exact same
> >> functionality. Is there any reason for carrying a fork of this any longer?
> >
> > Where is upstream for this, I'm not sure if I am following you? The only
> > active fork of ncurses-ruby (ncursesw-ruby) that I can find is ours -
> > which is now known as 'ncursesw' in gem world (ncursesw-sup has been
> > removed).
>
> It was late when I wrote this. What I mean, but did not manage to put in
> writing, is that the rmail-sup gem carries the same functionality. And my
> suggestion was that we adopt active maintainership of rmail.
>
> Sorry for the total confusion, I was tired...
>
> >> I understand that the in the future a migration away from rmail is planned.
> >> In the meantime, using rmail gem, could reduce complexity. Perhaps a
> >> similar move as with ncursesw-ruby can be made, adopting active
> >> maintainership? (I can volunteer for this!)
> >>
> >> As Matt states, rubymail is looking for active maintainership
> >>
> >> https://github.com/matta/rubymail/pull/2#issuecomment-33173575
> >>
> >
> > If you are up for it, that would be good, we might as well push directly
> > to RMail (and drop rmail-sup). I suggest you contact Matt and we migrate
> > the rmail-sup repoistory in sup-heliotrope (at github) to use the rmail
> > namespace. If he wants, we could also just move his repository to the
> > sup-heliotrope organization.
>
> I'll contact Matt and ask!
>
> > Please also make sure that the other maintainers of sup are
> > owners of the rmail gem so that it is not all dependant on one person.
>
> Absolutely!
Sounds good! If Matt agrees to make us maintainers, but wants to retain
the original repo, we can just rename the rmail-sup repo to rubymail
and revert the gemspec changes.
- gaute
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-01-29 9:00 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-01-28 1:18 [sup-devel] Rubymail maintainership Per Andersson
2014-01-28 7:55 ` Gaute Hope
2014-01-28 21:21 ` Per Andersson
2014-01-29 8:59 ` Gaute Hope
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox