• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Rob Spoor
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Carey Brown
Bartenders:

Data Storage

 
Rancher
Posts: 89
13
Scala Eclipse IDE MySQL Database Tomcat Server Chrome Java Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What ideas are their for how to store the source code and resources? Git on Github is pretty much the standard but there are other options as well.

-Zach
 
Saloon Keeper
Posts: 14662
330
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Regardless of the location, I think using a Git repository really is the best option. It will allow people to practice with a widely used and sane tool, without being afraid they'll break anything.

I also like Github because you can create a team there and put projects under that team, and you can easily configure what team members can push to what branches. That way, we can allow members to freely push to any feature branches they're working on, and require pull requests to stable branches.
 
Saloon Keeper
Posts: 5233
211
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Can't we start simple? It is not so easy to come up with a project, that is innovative and accessible to many. But I guess everyone has written a handy class, no matter what about, that could be sent in into some github collection. Points at hand: good javadoc, clear description, clear code. We can all try to learn from it, come up with some improvements, it doesn't matter what the subject is, and maybe we can distract some ideas for a follow up project. Hopefully we will see a broad spectrum of ideas and codes and styles.
 
Marshal
Posts: 77139
370
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Stephan is right: use Git. That allows us to track changes from the word go. If you try to track changes thereafter, it will be a dreadful job trying to put the work into a Git repository.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic