I got developer access to the tdbf sourceforge project and made the packages compile with all Delphi versions I have got

I got developer access to the tdbf sourceforge project and made the packages compile with all Delphi versions I have got
http://blog.dummzeuch.de/2013/07/27/tdbf-updates-help-required/

Comments

  1. Well done! If you want to give more exposure to TDBF and a better chance for developer contributions please release this to GitHub or Bitbucket in either git or Mercurial. These two sites make it so much easier for devs to contribute back to open source projects.

    ReplyDelete
  2. The problem with SourceForge is that it locked down and puts too many obstacles in front of developers to contribute back to a project. If you want to contribute to a SF project you need to somehow get in touch with the project admin. You can then provide patches to them and hope they have time to review and then apply it back to the repository. Alternatively, if you have a good reputation, you can gain maintainer/commit access to the repo directly.

    Given the number of hoops needed to jump through to actually update and contribute to the TDBF SourceForge project I must commend Thomas Mueller for his efforts.

    Seriously, move it to GitHub/Bitbucket.

    ReplyDelete
  3. I am not the project admin and I don't want to be that (I'll probably not even maintain it for long.), so I can't decide about where the source code is to be put. Apart from that: I actually like svn as a repository and especialy TortoiseSVN as client. Github supports only git and Bitbucket supports only git and Mercurial. Last time I locked I found the git clients way to complicated (so much for hoops to jump through). Now that Jedi moved to github, I'll probably have another look at git and TortoiseGit. I have not looked at Mercurial yet.

    ReplyDelete
  4. Subversion on its own is not so much of a problem (although I will say it can be a pain if you maintain several branches and do a lot of switching and merging between branches and trunk!).

    My beef is with the work flow employed with maintaining open source projects on SourceForge vs GitHub/BitBucket. GitHub and Bitbucket both allow you to clone other open-source repos. You can keep your repo up to date from the primary repo. You can also make changes and improvements to your own repo. You can also send back patches to the primary repo via a process called "pull-requests". Each one of these processes are both easy and simple for contributors and maintainers.

    The simple case is that GitHub and Bitbucket were built for making open collaboration on projects easy. Whereas SourceForge is good at managing projects for closed group. SourceForge start sucking when you need to interact with developers who don't have commit access to your project.

    SourceForge makes it easy for developers to checkout their own copy of a repo but it doesn't provide an easy avenue for someone to contribute back to a project.

    So many open source Delphi projects have been found abandoned on SF due to the fact that the admin has moved on to other things and that no one else has access to the project to keep up with the maintenance.

    ReplyDelete
  5. You can use tortoiseSVN (or any other SVN client) with GitHub if you like.

    https://github.com/blog/626-announcing-svn-support

    Also, for a nice looking free git/Mercurial client, just google for SourceTree from Atlassian.

    ReplyDelete
  6. Thanks for that hint. Currently checking out jvcl from github using tortoisesvn. So far, it seems to work. I wonder how it handles the externals...
    As for moving tdbf to github: It's not my project and I don't want it to be.

    ReplyDelete
  7. It doesn't. I guess that means I either stop contributing to Jedi or have to get used to git. Not that my contributions were large anyway..

    ReplyDelete
  8. What about Google Code? GitHub wiki and tracker markup just sucks for anything more complex than "HELP!!!11111"

    ReplyDelete
  9. Thomas for me it is different. I not always agreed with jvcl changes (and they - with my patches). Git at least in theory gives me way to easier go with fork. OTOH it has troubles with jedi.Inc from external repo, but this may be the case of rtfm or tortoise lacking something. PS. I wonder if I still have tdbf svn write grants. It would be funny.

    ReplyDelete

Post a Comment