[wildfly-dev] WildFly Community Space Replacement

James Perkins jperkins at redhat.com
Mon Feb 3 13:15:42 EST 2020


On Mon, Feb 3, 2020 at 1:02 AM Darran Lofthouse <darran.lofthouse at jboss.com>
wrote:

> I don't think we really need to separate wiki from articles, when we moved
> to the jboss.org infrastructure there was no real wiki solution so the
> closest you had was articles which some are created once similar to a blog
> but others were created to try and keep up to date so I think +1 for a wiki
> to hold the immediately updatable content.
>
> One issue with stackoverflow is everything must be in the format of a
> question with answers in the format of an answer, added to that when you
> ask a question you get more questions second guessing why you are asking
> the question rather than providing an answer!  It seems if we exclusively
> use stackoverflow we don't have a suitable place for general discussion
> unless you force them to be real time in Zulip or allow more general
> discussion on the dev list.  You mention moving developer discussion to
> google groups, why not allow the same for user discussion?
>

I think this makes sense to use Google Groups as well.


>
> I think it would be nice in general if we could find ways to encourage
> more general discussion in the community spaces so it is not just a place
> to visit with a question.
>
+1

>
> Presently blogs published to wildfly.org don't have an option for
> comments or ongoing discussion, having a user space could allow for a
> discussion to be started for a blog to allow ongoing collaboration.
>
> Regards,
> Darran Lofthouse.
>
>
> On Fri, Jan 31, 2020 at 8:27 PM James Perkins <jperkins at redhat.com> wrote:
>
>> Hello All,
>> We are in a position where we need to change the community space for
>> WildFly, currently located at https://developer.jboss.org/en/wildfly/.
>> On 2020-03-1 this community space will become read-only.
>>
>> We've got 3 areas we need to move.
>>
>>    1. Forums/Q&A
>>    2. Wiki/FAQ
>>    3. Articles
>>
>>
>> 1. Forums/Q&A
>> My preference here is we would use Stack Overflow, specifically the wildfly
>> tag <https://stackoverflow.com/questions/tagged/wildfly>. It seems the
>> forums is really more Q&A than anything.
>>
>> If we want to keep the forum and Q&A separate we could use Stack Overflow
>> for the Q&A and Google Groups for the forum. Though I don't really see much
>> difference between the forum and Q&A.
>>
>> 2. Wiki/FAQ
>> For this we could use GitHub Wiki here. For details see
>> https://help.github.com/en/github/building-a-strong-community/about-wikis
>> .
>>
>> 3. Articles
>> I don't know how often articles get created, but it doesn't look like
>> often. My suggestion would be that we just use wildfly.org for this.
>> These seem to be akin to blog posts.
>>
>> Another option could be better as without knowing the structure of how
>> wildfly.org is a bit of ask for the community to write an article/blog
>> post.
>>
>> Any other options or suggestions on any of these points are welcome.
>>
>>
>> Not required but I would also like to open for discussion moving the
>> wildfly-dev mailing list to Google Groups. What are others opinions on
>> this? It seems to get fairly low traffic as of now.
>>
>>
>>
>> --
>> James R. Perkins
>> JBoss by Red Hat
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>

-- 
James R. Perkins
JBoss by Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20200203/975a875d/attachment-0001.html 


More information about the wildfly-dev mailing list