> should there be a separate git for addons perhaps because they don't need the same packaging/distribution effort, or maybe due to licensing inconsistencies, or ???
> Or will svn continue to be the preferred method of contributing addons? svn is used for historical reasons, but at some point it makes sense to move to git. Licensing is different in that there is no generic licensing for addons. There may be specific licensing, e.g. for Jd. Otherwise, anyone can contribute and use addons. On 18 January 2016 at 09:47, 'Pascal Jasmin' via Programming < [email protected]> wrote: > I think the reference is in the download section, where Eric suggests that > a more "social process" (GPL3 cloned to github) could aggregate changes > there prior to submission for inclusion into "official" J. > > A question for me though is addons includes only jmf. > > should there be a separate git for addons perhaps because they don't need > the same packaging/distribution effort, or maybe due to licensing > inconsistencies, or ??? > > Or will svn continue to be the preferred method of contributing addons? > > > > > ----- Original Message ----- > From: Marshall Lochbaum <[email protected]> > To: [email protected] > Sent: Monday, January 18, 2016 12:36 PM > Subject: Re: [Jprogramming] J Source > > I don't see an answer there. It's important for users to be able to > clone, rather than just download, the repository, so that they are able > to update it easily and quickly. Then people who want to use the latest > J source can stay up to date and test out changes before they are > published in an official version. So, can non-contributors clone the > repository? > > Marshall > > On Sun, Jan 17, 2016 at 08:36:55PM -0500, Eric Iverson wrote: > > Continue reading on the page about Download and the git respositories. > > > > > > On Sun, Jan 17, 2016 at 8:25 PM, 'Jon Hough' via Programming > > <[email protected]> wrote: > > > This looks very interesting. Is it possible for non-contributors to > clone the repo? > > > > > > Also, I noticed from browsing the commit history that there is only > one branch. It might be better to make a develop branch and use something > like git-flow http://nvie.com/posts/a-successful-git-branching-model/ . > Just a suggestion. > > > > > > -------------------------------------------- > > > On Mon, 1/18/16, Eric Iverson <[email protected]> wrote: > > > > > > Subject: [Jprogramming] J Source > > > To: "Programming forum" <[email protected]> > > > Date: Monday, January 18, 2016, 9:33 AM > > > > > > If you have any interest in the J > > > Source please take a look at: > > > http://www.jsoftware.com/source.htm > > > > > > (press refresh if you don't see a "git repo" section) > > > ---------------------------------------------------------------------- > > > For information about J forums see > http://www.jsoftware.com/forums.htm > > > > ---------------------------------------------------------------------- > > > For information about J forums see http://www.jsoftware.com/forums.htm > > ---------------------------------------------------------------------- > > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
