:: Re: [Dng] Weekly developer status u…
Top Pagina
Delete this message
Reply to this message
Auteur: Jude Nelson
Datum:  
Aan: T.J. Duchene
CC: dng@lists.dyne.org
Onderwerp: Re: [Dng] Weekly developer status update
Hi T.J.,

That's kind of what's already been happening. The big push right now is in
pulling the Debian packages that depend on systemd into git.devuan.org and
altering them so they don't need systemd. All other Debian packages (the
ones with no direct systemd dependency) should "just work."

Jaromil has a list of Debian packages that need to be tweaked here:
https://git.devuan.org/devuan/devuan-project/issues/6. Each of these needs
a maintainer--at the minimum, the maintainer needs to ensure that the
package (1) is up-to-date with upstream (i..e "git pull" every now and
then), and (2) is set to compile without systemd. Jenkins takes care of
building the package automatically.

Hope this helps,
-Jude






On Sat, Feb 14, 2015 at 5:37 PM, T.J. Duchene <t.j.duchene@???> wrote:

>
> > I think this is a good idea, even if only to keep me motivated I'll
> > start.
>
> Thanks for the update, Jude. It is appreciated.
>
> I'll state from the outset this is entirely a suggestion. I think it may
> help
> get outsiders involved, but the concepts are entirely subjective.
>
>
> What I was really looking for though something like this:
>
> 1. The dev team creates a list of core packages that need to be in place
> for
> Devuan to boot. Core packages need not include anything related to X at
> this
> point, just what is needed to get to a terminal.
>
> 2. The dev team then posts a list of things needed to create an acceptable
> Devuan build environment.
>
> 3. Dev team posts a list of packages that need work.
>
> 4. People on the list express interest in taking them on.
>
> 5. Once finished they send them back to the dev team for assessment. If
> they
> decide things are good, then the package can be included in Devuan,
> otherwise
> not. If you do enough good work, then perhaps you might be invited as a
> core
> member someday.
>
> 6. Repeat step one, eventually with X, etc
>
> The idea that I am trying to endorse here is to extend communication to the
> wider community to speed work, without expanding the core dev team beyond
> manageable proportions.
>
> It might sound a bit like the core dev team is a bit of a dictatorship, but
> personally I'd rather have a meritocracy rather than a democracy at this
> point. Devuan needs people willing to actually do the needed work.
>
>
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>