Due to the massive influx of new people, all offering help in various ways, I think we need to start organising some teams, and have people from the original team as leads of those teams - there's just no way I can organise it all (and I wouldn't be able to do it all anyway). ?So these are the areas I see as being needed right now, comment if you think there are more:
Sys Admin. ?Running the web site/forums/wiki/discord. ?More from a technical standpoint than a moderation one. ?I've already have several offers for helping with bug trackers, and I'd like a blog to keep people more up to date (for now "open.mp" is "open communication", "open source" is later once we are better set up. ?This can also include build servers/CI/git.
Manager: Southclaws
Assistant: Jamie
Media. ?Screenshots and videos, blog posts, graphics, and general outreach. ?Again, quite web focused for now. ?I.e. Community. ?Start working on talking to existing servers. ?We should be seen as proactively engaging with them to get their feedback on what they want to see improved (especially bugs and pain-points), ?New features won't really be in the first version, but down-play that fact.
Manager: Potassium
Assistant: Kar
Modelling. ?SA:MP comes with models. ?We should too. ?Mostly because we want ways for people who can't code to contribute directly to the mod, also we can't use SA:MP's.
Manager: ???
Assistant: ???
Coding. ?This would be much simpler to distribute if we could load modules dynamically. ?Maybe I'll look more deeply in to that, then we can give out pre-built dev servers that people can test isolated modules against.
Manager: Y_Less
Assistant: hual
Scripting. ?Modes, includes, documentation, as before. ?Look in to refining the current API. ?We don't want many new features, but that doesn't mean we can't tighten up what's already there. ?Things like tag-safety, consistent naming, stuff we were discussing anyway here (these issues explain getting new APIs while keeping the old):
https://github.com/sampctl/pawn-stdlib/issues/7
https://github.com/sampctl/samp-stdlib/issues/18
https://github.com/sampctl/samp-stdlib/issues/15
Something else to work on is doing the same in reverse. ?Get a new set of includes for SA:MP out that backport the changes and renames so people can start using them straight away. ?The OMP version would be, say:
#pragma deprecated Use `PlayerText_Create`.
native PlayerText:CreatePlayerTextDraw(...) = PlayerText_Create;
native PlayerText:PlayerText_Create(...);
Since the native will be renamed internally. ?The back-ported version would be:
#pragma deprecated Use `PlayerText_Create`.
native PlayerText:CreatePlayerTextDraw(...);
native PlayerText:PlayerText_Create(...) = CreatePlayerTextDraw;
Thus giving the same outwards appearance in terms of API and warnings, but with different internal names.
Manager: Kristo
Assistant: CaioTJF
Moderation. ?Obviously requires more trusted members, but we can have people in charge of small sections. ?Should also have them post a lot to keep forum activity high. ?This includes forum features, whereas ops would include forum hardware and backups - a frontend/backend split. ?P.S. ?The current `edit` button is really annoying, since instead of just taking you to the post, it requires a second selection. ?As is the interstitial page after making a comment.
Manager: JustMichael
Assistant: spacemud
So say which part you're interested in managing and we can start setting up areas for these and leave you to manage those sub-sections fairly independently. ?Right now I feel like I'm not pulling my weight and being a bit of a bottleneck on progress (though seeing the forum just accelerate is amazing - thank you). ?If each person could start a private topic on their area, we can discuss in there what needs doing. ?From there I can leave them to get on with organising it. ?I'd then suggest opening a public topic as well to get other people involved and keep them informed of what's going on.
I've tentatively assigned people based on what they said. ?Kar, you said "anything not modelling", so you're on community. ?Bruno, I ran out of applicable jobs unfortunately, but coding will be a big one, and will split in to several parts eventually - core, server, and client.