SR3R Project Logistics and Recruitment, the SR3R way Options Track this topic Email this topic Print this topic Download this topic Subscribe to this forum Display Modes Outline Switch to: Standard Switch to: Linear+

[Kagetenshi]

As most of you probably know, the SR3R Project is moving to a new home. While we'll have Trac set up with an integrated wiki and Subversion repository, it seems to me we need side-channels for general kicking around of rules ideas and discussions that aren't solid enough to open a ticket for. The question is, what do we use?


Fora have the advantage of being all in one place and friendly to people outside the project in terms of looking over the material within. Also, everyone here is presumably familiar with how they work.

Downsides: people need to specifically take time to visit the forum and check for new posts. Can be a pain in the backside to administer. The only board I'm familiar with administrating has a bit of a reputation for poor security, and lacks various features for notification of new posts (for example, the ability to subscribe to an entire forum).


Mailing lists have the advantage of being push rather than pull. No need to set time out of your day to check for new material, just wait for the email to roll in.

Downsides: less familiar to most people, can become a burden if lists become highly-trafficked. Conventions for proper quoting of previous replies are a deeply contentious issue for some.


Something else is exactly what it says. You tell me what the advantages and disadvantages are :) just don't suggest wiki talk pages—we'll have them available, but after thinking about trying to seriously communicate via them I had to go sob in a corner for a few minutes.


Multiple options have the advantage of suiting the tastes of people who prefer different discussion formats. Their primary disadvantage comes from the division of the community and the necessity for those who wish to keep track of the full scope of activity (me, for example) to address each different venue.



Beyond that, we've got a few positions to explain and recruit for. Some positions are open for applicants, others are by invitation only, and others are already satisfactorily filled.



Benevolent Dictator for Life: Yours truly. Like a developer (see below), but with unilateral veto/override power (which I try not to use).

Recruitment status: closed.

Requirements: be me.



Developer: Those who administer the project and have a high degree of responsibility for evaluating changes. In general, changes will not be accepted if a developer is strongly against the change, and is mostly likely to be accepted if no developer is less than mildly in favour of the change.

Recruitment status: invitation only.

Requirements: high willingness to examine changes and their mathematical and logical consequences in a rigorous fashion, ability to effectively express the reasoning behind support for or opposition to a given change. Extensive familiarity with SR3 canon world and rules. Some familiarity with SR2 and SR1 world and rules. Familiarity with Earthdawn world a bonus. Ability to double as an editor (see below) a large bonus.

There will not be many developers, so don't be insulted if I don't offer you a spot. I still love you ;)



Legal advisor: someone with proper legal training and familiarity with trademark and copyright law to provide guidance and advise to the SR3R Project on maintaining a clear legal status. Willingness and ability to represent the SR3R Project (whether at normal or reduced rates) in the event of legal action is a bonus, but is neither required nor expected. In particular, while it would be nice, it is not required that an applicant provide (in the strict sense) legal advice.

Recruitment status: open.

Requirements: formal legal training and experience as a lawyer, paralegal, or legal document assistant.



Editor: those who maintain the actual rules, and who assist in transcribing new rules. Also maintain and create templates, and ensure clean presentation of the rules.

Recruitment status: open.

Requirements: experience with or willingness to learn LaTeX or ConTeXt. Previous typesetting experience a plus. I am willing to provide any assistance I can in the learning process.



Example writer: takes decided-on rules and writes clear, coherent, original examples demonstrating them in action. May produce new examples for canon rules, or assist in producing a new description for existing rules so as to eliminate copyright issues regarding their inclusion.

Recruitment status: open.

Requirements: proficiency with English language, ability to produce high-quality examples, willingness to learn at least basic LaTeX or ConTeXt.



Submitter: May help out with whatever's available or be brought on to work on a specific ruleset. Has commit access to the repository, but is generally expected to run changes by a developer.

Recruitment status: open, though most of these will probably be recruited in reaction to specific issues.

Requirements: must be able to partly fill at least one of the above roles, or to complete a specific task that may be outlined later.


And finally:



Interested Party: files tickets for rules that need fixing, rules that should be added, rules that don't align with flavour, flavour that doesn't align with rules, and picks apart both the current rules and their suggested replacements.

Recruitment status: universal. You join this group by paying attention to our project :)

Requirements: be interested, be involved. Submit reports of experience with using these rules. Pretty much do what you've already been doing in the SR3R threads.



Let me know if there are any questions, comments, or whatever.

~J