Fork me on GitHub
Not signed in (Sign In)

Welcome, Guest

Want to take part in these discussions? Sign in if you have an account, or apply for one below

New version announcements: Flint on GitHub

Bottom of Page

1 to 3 of 3

  1.  
    • CommentAuthorRichard
    • CommentTimeAug 31st 2010 edited
     
    I've moved the development of Flint from GoogleCode to GitHub. I will continue to maintain the GoogleCode repository for those that are used to using it, but active development will now take place on the GitHub repository, with updates to the GoogleCode repository when a new version is released.

    The GitHub repository is in two parts. The core, at http://github.com/richardlord/Flint, contains the source code for Flint. The second repository, at http://github.com/richardlord/Flint-examples, contains the examples. Documentation and compiled swcs are no longer in the repository but are available as downloads.

    If you want to use SVN but want to access the GitHub repository, this is possible although the repository can't be browsed so your SVN software will likely throw errors when doing anything other than check-out. The URLs for SVN access are http://svn.github.com/richardlord/Flint.git and http://svn.github.com/richardlord/Flint-examples.git.
  2.  
    Have you considered whether you'll accept patches and enhancements via Git? The workflow would run something like this:
    1) I create a forked copy of Flint in GitHub in my own account. Call this copy FlintRC for sake of argument.
    2) I add a new class or update an existing class in FlintRC (e.g. adding DictionaryInitializer, fixing a bug, or adding a usage example to the documentation.)
    3) I let you know about it, probably via the forum.
    4) You look at the change (on github) and decide to incorporate it via git's "pull" command (or not, hopefully adding a note to the forum)
    5) Alternately, when you issue an update, I can use "git pull" to copy the changes from Flint to FlintRC without losing my patches.

    How do you feel about this?
    • CommentAuthorRichard
    • CommentTimeSep 1st 2010
     
    Hi Richard

    That is the main reason for moving the repository to Git. It makes it much easier for others to collaborate. I assume that all content on GitHub is open to forking and pulling so didn't think to mention it specifically.

    One of my big problems with Flint is a lack of time to continue developing it. I try to answer questions and fix bugs in a timely manner but adding new features and improving existing features is something that I struggle to find time for. I hope that by moving the project to GitHub others may choose to develop it further without having to take on the responsibility of ownership, and the project can develop through the useful work of contributors like yourself.

    I look forward to seeing what you create. Now get forking.

    Richard

1 to 3 of 3

  1.