What are some good ways to collaborate on a plugin?

Discussion in 'WIP and Development Status' started by tylersyme, Sep 17, 2013.

Thread Status:
Not open for further replies.
  1. Offline


    Let's say I have 4 devs (including me), and I want to have all 4 of us work together to finish a project.
    I'm trying to picture how that would work, I mean, how would you keep it all organized instead of people going off and doing their own thing?

    I can think of the obvious
    1. have goals to reach
    2. give each dev specific task(s) to complete
    3. organize each task in the correct order

    I guess I'm looking for two things
    Resources that will make collaboration easier (such as live, auto-updating code)
    and, is there anything that I'm missing? I gave 3 things that I would probably do, but are there any pointers or tips that will make the collaboration go smoother?

    Thanks :)
  2. Offline


    I think this goes without saying, but of course a repository like github or bitbucket to store code in.
  3. Offline


    Just github + skype works great.
  4. Offline


    Trello is good for team organization.
    caelum19 likes this.
  5. Offline


    Very good commenting on each line of code :p
  6. Offline

    ZeusAllMighty11 Retired Staff


    Each line gets messy.. perhaps just the methods and any parts which will be used in an API
  7. Offline


    was just a joke but yeah heavy but suitable commenting is gd for readability
  8. Offline


    One leader, one team. You need to have a leader who will merge everything, and who will check if everything is good, and organized. But don't be an opressor. Your team will give you suggestions, consider those suggestions...
  9. Offline


    Make sure everyone put comments on on their work, it'll make the project much more efficient if you are able to sum up a paragraph in 2 words.
  10. Offline

    Hoolean Retired Staff

    Establish a service that you will use for each aspect of the project. E.g:

    Communication: IRC​
    Code Collaboration: GitHub​
    Issues/Bug/Ticket/TODO Handling: GitHub​
    Project Building: Jenkins​

    Next, assign roles in the group. E.g.

    • Leader - will assign roles and help with a little of each
    • Page handler - will keep BukkitDev / other public relations and documentation up to date
    • Issue handler - will answer user's questions etc
    • Developer(s) - will work on the project
    Bare in mind, the above suggestions are mainly valid for a large project. In a smaller one, contributors could share roles. But basically, ensure these fields are covered:
    • Issue Handling
    • Documentation
    • Development
    Axe2760 and Chinwe like this.
  11. Offline


    I loveeeeeeeeeeeeeeeeeee trello, Made by the same guy who made Stack Exchange too :)
Thread Status:
Not open for further replies.

Share This Page