#70 provide a general forum for the Peers Community
Затворени
отворен преди 6 години от bill-auger
·
17 коментара
Етикети
Няма етикет
Етап
Няма етап
Изпълнител
Няма изпълнител
4 участника
Зареждане...
Все още няма съдържание.
i like the idea of the new 'Peers' NaB organization
https://notabug.org/peers
it would be a memorable URL that could be used as a general forum for the community
I'm also OK with this idea. The only problem is that organizations in Gogs aren't really well structured (from a UI point of view), they are difficult to navigate. It would end up with all projects listed one after the other in a flat list. So for example, if some projects have more than one repository, they all get entangled in one single list of repositories.
zPlus -
i dont understand that concern - the only notable change i can see is the url:
how would that affect any other project?
@bill-auger I'm OK with the change. I'm only saying that if we move more projects/repos under the same "peers" namespace over time, it will become pretty messy pretty soon.
ok but as it is now, isnt it even "messier" to have them scattered around under various personal namespaces?
i was really only considering one repo to be used as a general forum for issues related to the community itself - that need not be this repo for the website except that it seems this is how this issue tracker is being used now
how many repos do you think would be candidates for the "peers" namespace other than the website? even the freepost website is not itself implicitly concerned with the peers community
A ML, a Discourse instance, or an instance of this software could be more appropriate spaces to use as forum than an issue tracker :)
right now, probably only this one.
you mean because of the domain name?
indeed i am really only suggesting some public forum to discuss issues related to the peers community itself - and yes the repo for the website is not ideal for that purpose but that seems to be now how it is being used
no i meant how many repos exist ONLY for the peers community and serving no other purpose - those would be the only ones that would best fit under the peers namespace - the freepost website serves a purpose of it's own beyond the peers community but this website would fit there appropriately (even if not to be used as a general forum)
is there an issue for creating a forum? maybe there should be one
my primary reason for this issue was to have some memorable url for asynchronous discussions - it seems like things are going more in that direction lately - with less general IRC chatter and more focus on "getting down to business" - im not particularly concerned with which software provides that functionality
a memorable URL something like one of these:
I have some of this already in mind. I was planning on either transferring or mirroring (either with git mirrors or with gogs mirrors) all the peers projects to the nab organization. I need a little bit of time to decide which seems better. And in addition, I already have a git repo; peers.community already has its own git repositories, though I haven't had time to make them public. Not enough time to maintain it at the moment. It feels like a lower priority to centralize to the domain name.
Let me read the rest of these comments and write back more later about forums etc.
Sorry, I'm still pretty bogged down with work. There's also a couple other tasks I have, peers related that are time sensitive at the moment. I have not forgotten and I will come back to this about the forums and restructuring the git repos soon.
You mean, something like Salon from Liberapay.
Yeah, I like the idea. The community is still small, so we don't need big forum software right now.
I've started chiseling this. I started with the template. I will do the rest of the website next. Let me know if you have any ideas. I think I'd like to leave this repo up as a legacy for a while with a note on the move. And of course, I will update the reference on the peers home page. I'll probably rename the new repo to peers-www.
EDIT:
I supposed I could have done this instead of what I did:
Created the peers-www repository.
I think this is a good idea. Let me know if you need anything for the notabug.org/peers organization page (you should be fine though, I've added you as "owner").
regarding
git filter-branchthat is a nice option in that the commit history is preservedthere seems to be multiple feature being discussed here so i just wanted to clarify exactly what i meant with this issue
the reason for this issue was that it is in fact this repo contains the code for the peers website but this issue tracker is currently being used as a general forum for any issues related to the peers community and not only bug/suggestions related to the website
it is true that regardless of its purpose, it is not clear from the URL being under the 'vaeringjar' namespace that it is "official" - that would be more clear if it were under the 'peers' namespace - but the bigger issue is that this issue tracker is being used as a general purpose forum so i was actually proposing a new empty repo to be used only as a discussion forum
the comments from today are focused changing to a more memorable "official" namespace but renaming the repo to 'peers/peers-www' does not solve the vagueness issue of whether it is the appropriate fora for discussions related to the peers group generally - indeed it makes it more clear that it should not be used as a general forum
it was mentioned that a proper forum software is being considered and the existence of such a dedicated forum would address my concern in this issue 100% but as jorge mentioned it may be overkill for now - that is why i suggested an empty repo as a simple temporary solution e.g. https://notabug.org/peers/community/issues
This makes sense. So for that part, discussing Peers as for the community, I feel like that sort should move either to freepo.st or to the peers kanban. I will set a better example and update it more frequently and transfer the remaining issues to their appropriate location.
When I get home I will also grant access to bill-auger and jorgesule.
If folks would rather a forum instead of the kanban, or a different kanban, we can talk about that part too.
yes those are all different tools for different jobs though
freepost is a essentially an old-school BBS or news stack - as such, issues get buried quickly and there is no metadata to manage them - so not ideal for ongoing discussions and inappropriate for development/project management which should be more static and malleable
kanban is an agile workflow tracker for management and discussion of development tasks that are currently being worked on - or that work is agreed upon to be desired and scheduled or otherwise pending - but not for discussion/proposals of issues for which no clear need or plan is yet agreed upon
a bug tracker like this page - is something different yet - it exists as a triage staging area for bugs/feature requests that are not yet verified as existing bugs or desired new features - once they are verified, they would be promoted to a task/story on the agile tracker (if there is one) and assigned a severity/priority
and of course, a forum or mailing list is for everything else in general that does not fit one of the above categories
as i understand there is kanban board and of course freepost, this bug tracker is currently filling the roles of both a forum and as the bug tracker for the website - so it seems the only thing left to do is a distinct site for a forum, if and when that is deemed necessary to split those concerns
Okay. So I think for now, instead of spreading us out, and also to address the clarification of branding, let's use that idea move all additional conversations to peers-forum.