Hi, so far, I sent a message to every former member of contrib to inform them of the switch to the new contrib. Today we will replace the old contrib with the new one. In addition to this our new application scheme will also start this week and that means that we will check new applications from now on! Regards Simon
On Sun, Nov 05, 2006 at 07:14:56PM +0100, Mark Rosenstand wrote:
On Sun, 2006-11-05 at 16:34 +0100, Simon Gloßner wrote:
In addition to this our new application scheme will also start this week and that means that we will check new applications from now on!
'Applications' in what sense? Programs?
No, application means an application for becoming a member of the contrib repository. [1] [1] http://crux.nu/Main/ContribRules
On Sun, 5 Nov 2006 16:34:40 +0100 Simon Gloßner <viper@hometux.de> wrote:
Hi,
so far, I sent a message to every former member of contrib to inform them of the switch to the new contrib. Today we will replace the old contrib with the new one. In addition to this our new application scheme will also start this week and that means that we will check new applications from now on!
Seems there is very few ports in new contrib so far. I can't believe other maintainers gave up or not followed the list... Another question is how someone can know if particular maintainer just postponed his git/contrib participation or completely retired... so that another maintainer can take over his ports? P.S. I hope the current sate of (old) contrib repo will be available through rsync as contrib-attic for some time. At least this will allow new users to get more (not very fresh) ports putting contrib-attic after contrib in prt-get.conf -- Mikhail Kolesnik ICQ: 260259143 IRC: mike_k at freenode/#crux, rusnet/#yalta Jabber: mike_k@jabber.lafox.net NIC handle: MKK83-UANIC
On Mon, Nov 06, 2006 at 12:16:14PM +0200, Mikhail Kolesnik wrote:
Another question is how someone can know if particular maintainer just postponed his git/contrib participation or completely retired... so that another maintainer can take over his ports? I think that the maintainer will announce his retirement at the mailing list. Besides orphaned ports are moved to attic.
P.S. I hope the current sate of (old) contrib repo will be available through rsync as contrib-attic for some time. At least this will allow new users to get more (not very fresh) ports putting contrib-attic after contrib in prt-get.conf Well, I think that this is only a good idea if we use this repo as another attic repo. We shouldn't provide old and possible harmful ports to new users.
Regards
On Mon, Nov 06, 2006 at 12:16:14PM +0200, Mikhail Kolesnik wrote:
Another question is how someone can know if particular maintainer just postponed his git/contrib participation or completely retired... so that another maintainer can take over his ports? I think that the maintainer will announce his retirement at the mailing list. Besides orphaned ports are moved to attic. I doubt we'll see any such announces in a week or two, but the fact is
Hello, Simon. On Mon, 6 Nov 2006 12:34:01 +0100 Simon Gloßner <viper@hometux.de> wrote: that very few contirb members started to use git.
P.S. I hope the current sate of (old) contrib repo will be available through rsync as contrib-attic for some time. At least this will allow new users to get more (not very fresh) ports putting contrib-attic after contrib in prt-get.conf Well, I think that this is only a good idea if we use this repo as another attic repo. We shouldn't provide old and possible harmful ports to new users. Of course we should not. But imagine a new user a with a freshly installed crux 2.2 system - he'll definitely miss many common applications. What is the plan for him? Sync to many-many personal repos or reinvent all that ports by hand?
Personally I am ok with your plan and waiting for others to switch. -- Mikhail Kolesnik ICQ: 260259143 IRC: mike_k at freenode/#crux, rusnet/#yalta Jabber: mike_k@jabber.lafox.net NIC handle: MKK83-UANIC
On Mon, Nov 06, 2006 at 02:11:05PM +0200, Mikhail Kolesnik wrote:
Another question is how someone can know if particular maintainer just postponed his git/contrib participation or completely retired... so that another maintainer can take over his ports? I think that the maintainer will announce his retirement at the mailing list. Besides orphaned ports are moved to attic. I doubt we'll see any such announces in a week or two, but the fact is
On Mon, Nov 06, 2006 at 12:16:14PM +0200, Mikhail Kolesnik wrote: that very few contirb members started to use git. Seems that i didn't get your point. In my opinion members of the _new_ git contrib repo will announce their retirement to the mailing list.
I hope the current sate of (old) contrib repo will be available through rsync as contrib-attic for some time. At least this will allow new users to get more (not very fresh) ports putting contrib-attic after contrib in prt-get.conf Well, I think that this is only a good idea if we use this repo as another attic repo. We shouldn't provide old and possible harmful ports to new users. Of course we should not. But imagine a new user a with a freshly installed crux 2.2 system - he'll definitely miss many common applications. What is the plan for him? Sync to many-many personal repos or reinvent all that ports by hand? Well, there is no plan. If he miss something he has to create the ports on himself or sync to personal repos...
Hey, On Mon, Nov 06, 2006 at 13:20:05 +0100, Simon Gloßner wrote:
On Mon, Nov 06, 2006 at 02:11:05PM +0200, Mikhail Kolesnik wrote:
Another question is how someone can know if particular maintainer just postponed his git/contrib participation or completely retired... so that another maintainer can take over his ports? I think that the maintainer will announce his retirement at the mailing list. Besides orphaned ports are moved to attic. I doubt we'll see any such announces in a week or two, but the fact is
On Mon, Nov 06, 2006 at 12:16:14PM +0200, Mikhail Kolesnik wrote: that very few contirb members started to use git. Seems that i didn't get your point. In my opinion members of the _new_ git contrib repo will announce their retirement to the mailing list.
Either way I think it would make sense to have a wiki page listing contrib maintainers along with their git username, flyspray account name and public wiki user name (if any). Regards, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch
participants (4)
-
Johannes Winkelmann -
Mark Rosenstand -
Mikhail Kolesnik -
Simon Gloßner