In regard to bug-tracking & fixing, is there any reason not to use github
as the source repo?
There are a lot of advantages to using github or bitbucket as the open
source repo.
- git-based version control
- easy branch management
- cloning repos is simple
- forking repos is simple
- tracking changes between branches & forks is easy
- pull-requests supported for accepting changes from forked repos
- with sufficient test coverage, a continuous integration system can be
applied on specific branches
- built-in and easy gist (code snippets) sharing
- there is optional issue tracking
- there is an optional, attached wiki (also managed via git)
- access can be controlled as read-only and read-write
- a "core" group of users with write-perms on the repo
- both github and bitbucket are commercially supported, and have been
adopted by many companies as the preferred version control source
- on both github or bitbucket, as an open-source project, it would be
free
- The owner login should probably be called "jsoftware" or "j_software",
- there is an existing login called "jsoftware", which appears to
have been created in Jan 2011.
- other than a "test" (also created in Jan, 2011), there are no repos
in the "jsoftware".
- It appears to have been created by Ken Lettow
- Regardless of which account owns the primary J software repo, some
other suggestions for management:
- the core contributors could be given read-write access to the new
repo
- the public would have read-only access
- there should be a feature branch for each new feature
- changes to the "master" branch would be accomplished by pull
requests (PRs) from forked repos
- don't accept PRs without tests
- Enable the issue-tracking feature on the J software repo, so issues
can be filed, tracked, assigned, commented, closed, etc.
Just a thought.
If any help is needed in setting it up and/or managing the repo, I'm
offering it.
--
Best regards,
Alan
On Fri, Dec 18, 2015 at 6:23 AM, Eric Iverson <[email protected]>
wrote:
> As soon as we get j804 release out we will move on getting new source
> and infrastructure available. This should be in place early in the new
> year.
>
> On Thu, Dec 17, 2015 at 10:29 PM, Joe Bogner <[email protected]> wrote:
> > Might be a relevant time to ask for an update on the git repo for J
> > GPL source:
> http://www.jsoftware.com/pipermail/chat/2015-June/006648.html
> >
> > I haven't heard anything since June. Is there an update?
> >
> > On Thu, Dec 17, 2015 at 10:26 PM, bill lam <[email protected]> wrote:
> >> I think this bug is serious. If anyone can provide a patch
> >> based on the j701 GPL source and related test script,
> >> then I can merge the fix into the next release.
>
--
Best regards,
Alan
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
