Wedge
Public area => The Pub => Plugins => Topic started by: Arantor on September 30th, 2011, 10:54 AM
-
Well, I've been toying around with a list of plugins I want to write, stuff that I don't want in the core but stuff I want to have available.
The question for me is how I manage development; using version control is a given, and I'm used to working with SVN. But I'm wondering if I should maybe try using Github, though I'm not really enthusiastic about opening the source to people until I'm happy to release it and traditionally I've not been happy about people breaking the things I've written (as used to happen), and I'm also feeling a bit burned after mods of mine got tweaked and republished without my permission.
So, what I guess I'm saying is that I'm leaning towards SVN and closed development still, but if anyone has any strong reason to convince me, please speak up!
-
I'd also go for SVN and hidden development but that's also me being shy in not wanting to give everyone an update on what I'm up to.
-
Just throwing this into the pot for you Arantor, but have you considered BitBucket/Mercurial?
Bitbucket don't mind you having private repositories (up to five, if memory serves) on their free accounts, and I personally find the Mercurial workflow really easy and obvious (where Git confused the hell outta me).
Just a thought...
-
On my RepositoryHosting account, I have a choice of SVN, Git or Mercurial so it's not like I can't experiment, but I'm more looking at whether it's worth making things open, especially as I heard that Niko made his wiki, arcade and PT available on Github.
But yeah, I'm still feeling in agreement with live about keeping closed dev :/ I tend to prefer issuing milestone builds, or at least having interim build periods - when working on SD, I found that having daily and twice-daily builds worked quite well for me in terms of setting goals, but that having the sense that anyone could watch over my shoulder and then give me changes doesn't sit right with me; working with someone up front as a co-developer is one thing, having any old person coming along and trying to proactively submit changes at me is another, and the latter is something I don't think I'm ready for...
-
Meh... go for SVN and let the licenses speak to what others can/can't do with your code.
-
That's where I was going; no-one's forcing or even asking me to do any different ;) I was just curious whether there was any benefit to anyone by me doing that sort of thing.
-
Pete, it's your code. Deal with it however you feel comfy with :)
-
I guess there is a part of me trying to pre-empt discussions, debates and crap that will inevitably come along... but yeah, I'm happy with the route I was likely to take anyway, and have already set up my repo for my plugins (since there's no need to have a repo per plugin unless it's a huge plugin like WD)
-
Just an FYI for anyone looking to centralise whilst still being distributed:-
Bitbucket now supports Git repos in addition to Mercurial! All the features you expect from Bitbucket, with unlimited private repos for free.
-
With a limit to 5 users, though! But it's nice to know.
-
Alternatively I can still use RepositoryHosting ;) Sure, it's not free (but is only $6/month) but the choice of SVN, Mercurial and Git, with more control over the number of users/permissions etc... makes it fairly hard to beat short of running it myself.
-
I use Assembla free SVN. It also has free Mercurial and Git.
-
I use github, it's a little expensive but I like it.
-
I use BitBucket, unlimited private repos for free account. Recently it added Git support.
-
I use BitBucket, unlimited private repos for free account. Recently it added Git support.
Like Nao responded, however, that's only for 5 committing users per repos. If your dev team is/are bigger than that, you need to give them cash money. For me, though, that's just perfect, none of the projects I'm working on have teams that big (one or two person(s) at most on our projects).
-
It's all academic in my case since my account hosts quite a few repos, not all of them actively mine, and I think there are more than 5 people that in total have commit rights across all the projects that are there...
-
Ah.. sorry I must have overlooked that, only reading must recent discussion :) maybe Wedge can apply Community License? http://www.atlassian.com/software/views/community-license-request.jsp
-
Thanks for the nudge but I've used JIRA before in my former professional capacity and I'm sure the phrase 'over my dead body' is involved...
Through my RepositoryHosting account, I have access to Trac, and we don't use that. SimpleDesk, though heavily modified, is installed here and we don't use that either...