VergeDev Guidelines
Displaying 1-2 of 2 total.
1
Please enter a numerical value for the importance of this sticky.
Enter 0 to unsticky.
Jesse

As discussed in IRC, the following sound like good ideas for vergedev:

- regular builds, possibly tags in SVN
- devs should discuss with each other before implementing a new feature or bugfix
- each commit should be a single bugfix or feature
- changelog.txt in SVN, gets updated with changes and explanation
- comments go at spot of change

People that do not have commit privs can send patches to vergedev folks.

Discuss?

Posted on 2005-12-11 14:10:17

mcgrue

I set up a email forwarder for sourcemaster@verge-rpg.com (or somesuch, it's in one of the files in the SVN atm). Right now it points to me, but I'll point it to whomever is going to be the high muckymuck of the main line at any given time.

I figured non-trusted modders could either email there or post in this forum for review and integration.

I also figured that, over time, awesome modders that we grew to trust would have full tree access, with the consent of the active devs.

Posted on 2005-12-11 16:58:03


Displaying 1-2 of 2 total.
1
 
Newest messages

Ben McGraw's lovingly crafted this website from scratch for years.
It's a lot prettier this go around because of Jon Wofford.
Verge-rpg.com is a member of the lunarnet irc network, and would like to take this opportunity to remind you that regardless how babies taste, it is wrong to eat them.