I think a Geo subcategory would be good. Basically anything that could have its own mailing list seems like a candidate for a domain subcategory.
I wish there was a way to delegate administration of subcategories, but there doesnât seem to be. As more people use this system, theyâll automatically gain trust and moderation capabilities though, so I think this will start to resolve itself.
Iâm not sure if you are looking for suggestions in this thread, but maybe a separate âAnnouncementâ forum where people can follow package tagging and news.
Ok, so once a Geo subcategory is created we would transition there, since there were no complaints on the julia-geo mailing list.
Geo domain created: Geo - JuliaLang. Please edit the About Geo page as appropriate â Iâve made it a wiki, which should let people edit it as I understand things, but if that doesnât work, let me know.
Whatâs wrong with low traffic categories, as long as they do have some?
Suppose that in the future a not-yet-existing subcategory acquires traffic withing an existing big category. How do we expect to ever make the split reasonable, if discouragement is our criterion? Cause the old big category will still have more traffic than any new one (as is the case with Usage anyway), so that discouragement will always stay in place. Or who will bother discovering and moving the past relevant threads from the chaotic big category to the new subcategory? Therefore weâll get stuck to the few categories decided early. Is that desirable? Do you have a different positive scenario in mind? Or does current consensus fail the whole concept of categories?
If the subject of a category is worthy to subscribe to, then low traffic is a plus, not a minus!
The only encouragement to use a category is for it to exist. If users end up not categorizing their posts and moderators end up moving many threads all the time, why not give moderators more categories to work with, along with giving users more specialized subscription options?
Forums create new subcategories all the time without this problem? Subcategoeries get made with mod help for a bit moving relevant topics, and people quickly switch. Hasnât that always worked pretty well?
What hasnât worked is creating too many categories. Julia-jobs? Julia-math? I could keep listing. When it splits too far it makes the community look inactive and makes everyone use one thread in order to get someone to actually read everything: Julia-users. So we know that method doesnât work correctly.
Following up on the Audio category: was that really necessary?
https://groups.google.com/forum/#!searchin/julia-users/audio|sort:relevance
There have been 33 posts in Julia-users with the word âaudioâ in its whole run. The majority of that is picking up posts which just have the word audio in it. JuliaAudio is an org, but itâs a small org without much usage yet (at least judging by the admittedly bad indicator of stars).
Telling people to post their 4 posts a year in such a small category is a good way to have no one read it, which defeats the purpose of the category. If every 4-5 posts per year topic is a separate category, there will be tons of categories most people wonât read, so most people wonât respond in, and so everyone will just post in the main forum. They need to be at least populated enough to be useful.
I think the solution that is going to work best for now is that we donât over design what categories we have, but rather use tags to classify topics. If a certain domain/topic arises often enough we then create a category for those posts.
Also if a community wants to move to discourse e.g. julia-stats, or JuliaGPU, we can create a specific subcategory.
What you describe is valid only for small communities, which may easily switch and may indeed look inactive at times. Itâs the exact opposite with big ones. A big community is very hard to switch and a bunch of low traffic forums cannot trick anyone into believing that the overall community is inactive. Unless someone hopes for Julia to stay small, it would be wise to look at the rate overall Julia traffic increases, even while currently being fragmented. Discourse cannot worsen things, only improve them. But as traffic increases (and Discourse will increase traffic even by itself), so does noise. Low noise is different from silence and can be a blessing.
And having people read what they donât want to read (i.e. noise) defeats the purpose of the categories as well. We donât tell people anything particular, cause chances are that people wonât listen anyway. Categories are mostly for subscriptions and proper movement of threads will be performed by moderators. There wonât be a single category without at least one moderator subscribed to it, so every single post will get read. Of course reading doesnât guarantee a good answer, but thatâs true for the main forum too.
Moreover, what most people miss is that Discourse is also a wiki. Can you imagine a wiki without specialized categories? Or should we defeat the purpose of wikis too? Iâm afraid that most people jumped into the new platform thinking of it as just a little better than google-groups, without reading the features of the new platform nor the full reasoning for and vision behind the migration.
Actually, a stated part of the vision behind the migration to Discourse or Statement of intent is that we want to invite, motivate and integrate the whole Julia community to the new platform.
UPDATE: Although in theory integration has many benefits and is the ideal, in practice independence is too precious to sacrifice. Therefore, I no more support integration.
I am pretty sure that a pinned post and mod intervention can easily make a big community switch to a new active forum in 14 days. Just a gut feeling.
I have had people tell me that, by looking at the inactive Julia-jobs, there must be no opportunities in Julia right now (which is completely false, just develop in Julia for a bit and the emails will start rolling in). So⌠it can?
I missed that because I donât care about wikis most of the time. I just want LaTeX/KaTeX. Literally, whatever forum has LaTeX is the best one. At least we now have pretty-looking code.
Thanks for clearing up that your objection is based either on âgut feelingâ or rumors or lack of much care for anything beyond personal convenience. My own experience and research on the matter is way different (internet is a big place, so maybe we experienced very different parts of it). Please donât take that as a personal accusation, cause you are not alone, most users just want to do their jobs, not having time to read such things. We hope in Discourse to better inspire the concept of the online community beyond that of an old-fashioned forum. There is no guarantee that this effort will succeed, but I believe that itâs worthy (else I wouldnât bother myself with threads like this one, I value my time like everyone else).
Thank you all for your comments and feedback, I found them very valuable.
Right now I am trying to make Discourse a good fit for the Julia community, so different opinions are doubly valuable.
Please remember to be civil and respectful to each other, as well as interacting on the basis of good faith.
Hey all,
Iâd also like to suggest a âToolingâ or âToolsâ category. That category would be for discussion about the repos in JuliaEditorSupport and similar (Eclipse plugins and whatever else may be out there); we could even move discuss.junolab.org over here, if thereâs interest.
Hi Ismael, I share your opinion regarding this topic. Having a specific language categories will extend the Julia user community.
I agree whole heartedly with those. Now that thereâs a Julia Discourse, it would be easier to follow the Juno discourse if it was here. Also, Julia is international and so we should accomodate other languages however possible.
Moving the Juno discourse over here would be good but it doesnât quite feel right under Domains. Maybe a Projects top-level category with Projects/Juno as the first subcategory and discussion of Juno can occur there?
Now thatâs the proper spirit for this thread and this community, thanks to everyone! Keep those categories coming and let the fragmented venues migrate and integrate into the new platform.
UPDATE: Although in theory integration has many benefits and is the ideal, in practice independence is too precious to sacrifice. Therefore, I no more support integration.
Well, the Domains description does say
Discussion of Julia in various specialized subject domains: statistics, optimization, machine learning, linear algebra, networking, GPUs, IDEs, etc.
but I agree that Domains doesnât seem like the right category for this. Projects/Juno sounds fine, but Iâm not quite sure yet what else could go in there as opposed to one of the Domains. Not that thatâs a reason to not do it though