Re: [Dragora-users] New branch for recipes?

[Matias Fonzo]

Hello Diego,

On Tue, 17 Apr 2018 08:28:49 -0400
Synchro <address@hidden> wrote:
> 
> I am also interested in this, I just find the master branch in the scm
> (notabug, and savannah) for recipes made from community, we will
> follow the fork, and pull request approach ? or sending a patch to
> the mailing list ? 
> 
> As I understand will be a difference between official recipes and
> community recipes, or do I get this wrong ?

Both channels are open (mailing list, git repos).  You can send pull
requests using notabug/savannah.  Notabug can facilitate the job via
web interface.

What I see is that any recipe not included on the master branch could be
considered as 'community', in the sense that the system can be expanded
(later).  Right now the priority is to try to make and offer a more
complete distribution.  The intended criteria is to complete for
example, the printing support, the networking support, offer the most
essential SCMs, gnupg, etc. the limit size is 700MB (ISO).

> Regards
> 
> On Tue, 10 Apr 2018 20:02:44 -0300
> Matias Fonzo <address@hidden> wrote:
> 
> > Ping?
> > 
> > On Mon, 19 Mar 2018 17:47:58 -0300
> > Matias Fonzo <address@hidden> wrote:
> >   
> > > On Mon, 19 Mar 2018 19:31:48 +0000
> > > Lucas Sköldqvist <address@hidden> wrote:
> > >     
> > > > selk wrote:      
> > > > > The new branch 'fresh' has been created.  Right now, is a copy
> > > > > of the 'master' or production branch.  It will be better if we
> > > > > give priority according to what the main branch needs.  For
> > > > > recipes coming from the community, perhaps we would need a
> > > > > separate repository...        
> > > > 
> > > > So it is OK to put a recipe for fossil-scm in
> > > > 
> > > >   https://notabug.org/dragora/dragora/src/fresh/recipes/devel
> > > > 
> > > > And then we merge it into master? Or put in master directly?
> > > > 
> > > > I'm a little confused :-)      
> > > 
> > > Well.. yes, that's another option, commiting it in master
> > > directly, testing, while giving priority to what is missing in the
> > > distribution.
> > > 
> > > The idea of the 'fresh' branch was to commit in it, testing, and
> > > if it's good add merge into master.  But there is no problem, for
> > > the sake of the work-in-progress.
> > > 
> > > Sounds good?
> > > 
> > >     
> > 
> >   
>