Greetings All,
This email has been a long time in coming. The coding team has been idle for the last long while, and we're making some efforts to change that now. We're trying to wrap up some patches for Bahamut 1.8.5 and hoping to begin some significant development over the next few months.
There are some big changes to how we're approaching things. In the past, we've run the Coding Team as a fairly closed unit - we worked on our development, took suggestions, and generally did most of everything ourselves. These days, we simply don't have the time to run things as they used to run. Changes are required - and so, along with some other things, we're changing our development process. This will result in the dalnet-src@dal.net mailing list becoming (I hope) a lot more active.
With that said, here are some more specific details:
Version Control: Git ===============
After many years of subversion and, before that, CVS, we've decided to switch to git for version control. Git is a distributed version control system written by Linus Torvalds specifically for the linux kernel. It applies very well to open source development as a general statement, and it will provide some flexibility to our development methods. For more information about git, check out http://git.or.cz
My copy, the master public copy for bahamut, is located at http://code.dal.net/bahamut.git
Git changes how development happens. Learn it, it is generally awesome.
Development Method: Maintainer ==========================
This is a bit of a departure for us. Since the team as a whole doesn't have a lot of time, myself included, we're changing a bit of the approach. I will maintain the master git repository, cut official versions, and push changes onto DALnet as things progress - nobody else will really have access to the main tree.
Keep in mind, using git, everyone has a full copy of the tree -- including all of the history. The only reason my tree is the main tree is because I say so, and everyone else lets me continue my delusions of importance.
The method of getting a change into my tree will be as follows:
1. Submit a patch series ---> email, to dalnet-src@dal.net, a series of git-generated patches of the changes you wish to make. Its probably a good idea to send a precursor email to explain what the patches are and why, so we know. ---> include a git location for me to syncronize with your git tree. I should be able to git-pull your changes into the master tree in step 3... 2. Public review ---> everyone is encouraged to review and comment on the patches or series of patches ---> This may mean that your patches are rejected and/or changes are requested to your patchset 3. git pull ---> I will pull your changes from your git tree, and merge them into the main tree
A few notes, to help with getting your patch to me in the best possible method:
- Explain what you're doing, and why. Each patch should be either a single change, or part of a patchset of a larger change. - Commit log messages are important. - DONT combine several different logical changes into a single patch. If they're more than one old 'changelog' entry, you're doing it wrong. - Follow the coding format rules. This will be slack to begin with, but I'm going to be spending some time fixing this up over the next little while. Once our code is cleaner, the rules will be more enforced.
Development Direction =================
Right now, we're going to concentrate on getting out version 1.8.5. Kobi has been working on a series of small patches to clean up a few outstanding issues in 1.8.4, and we should wrap this up within a month or so. These are small bugs and small enhancements.
Afterwards, we have some general goals (like IPv6, client side ssl, etc) but no specific list. I'm open to suggestions, and would love to get more people involved. Anyone is welcome to contribute. I'm looking at you, dalnet ops people, to try and give us some suggestions of features you'd want. And perhaps to code them yourselves!
I hope this will help breath some life back into the Bahamut community - I'd love to see this ircd become a major player again. We've always been one of the best in performance - we just have lagged behind in features for a while. Lets get this going again!
Thanks, epiphani Coding Team Lead
I can't remember if this was discussed a few years ago, or if I dreamt the whole thing... How about regex bans? I think it would go a long way towards helping to keep the bots at bay.
Aaron Wiebe wrote: <lots of cool stuff>
Is there some particular reason to switch from subversion to git other than Linus making it? I can't even fathom how having an entire copy of the the repository is useful, except for the purposes of an administrative backup.
It is similar to a subversion check out, with the exception that your check out can also be used as a repository and people can sync their copy with your changes.
It also makes it easier to merge changes especially if you have custom code.
On Oct 29, 2008, at 9:09 PM, Michael Reynolds wrote:
Is there some particular reason to switch from subversion to git other than Linus making it? I can't even fathom how having an entire copy of the the repository is useful, except for the purposes of an administrative backup. _______________________________________________ DALnet-src mailing list DALnet-src@lists.dal.net https://lists.dal.net/mailman/listinfo/dalnet-src
On Wed, Oct 29, 2008 at 9:09 PM, Michael Reynolds michael.reynolds@gmail.com wrote:
Is there some particular reason to switch from subversion to git other than Linus making it? I can't even fathom how having an entire copy of the the repository is useful, except for the purposes of an administrative backup.
There are several reasons - and one of them IS having multiple remote copies of the repository. In the past, we've had problems getting the resources together to maintain a constant central repository for dalnet code. Now I'm supporting it out of my own pocket, but in the midst of that mess, getting the repository back has often been difficult. Suddenly a server that was sponsored gets simply unplugged, and getting our data off of that machine has been difficult. This avoids the whole problem - and also doesn't make me personally responsible for the entire history of Bahamut's source tree (since I'm now providing the server for it).
But that reason alone wouldn't be a good reason to switch. I started using git about a year ago, and it changes how you think about source code management and version control. I like it for a few big reasons:
- Consistent history. Everything is always a progression - each change is small and identifiable, and you can -alter- history. - Ability to do big changes in multiple commits without affecting anyone else. I used to commit half-finished code all the time. Otherwise I'd be doing an absolutely massive commit later. - Really really fast. Branches are cheap, and this changes how you work again.
At the end of the day, it has the same basic features as subversion, and a whole bunch more that make things so much easier. It doesn't force you to change your methods, but it -supports- a superior model of doing things.
-epi
-
Aaron Wiebe -
Kevin Buley -
Michael Reynolds -
Sheik