[NFBCS] Making a plan

[Bryan Duarte]

Hello all,

I like to stay out of the confrontation but I am all for being a part of the solution. I think it is a great idea to have a website and/or wiki. I believe they both have their purpose and are useful in different ways. I feel we can and should do both but first we need to put our heads together and organize. Getting the server space, domain, and platform is easy as the people who handle that are a part of this organization, division, and list. Once we have the method and place the questions become, what content will we be populating the website and/or wiki with, by who, and when?

• Content: what content do we want to share? I do not feel a free for all in this matter would be ideal. Can we put our heads together on some common topics of interest to begin with? I have heard several people talk about Linux server admin, perhaps some useful tools, methods, or tips/tricks in that arena would be a good starting point. Beyond that we can branch off with different operating systems, tools, or topics. The main thing here is to determine what is going to be our main thing?
• Roles: who will be responsible for managing the content? I understand there is an open contributing protocol for wiki's under normal circumstances but as we are a division of the National Federation of the Blind I feel it might be best if we have a team who is responsible for managing content. This does not mean they are responsible for producing the content only that there is a central team who will manage the publishing of the content.
• Timeline: we should come up with a road map and timeline for when and how content gets published. We can determine what topics we want to begin with, call for authors, and set a time frame for when submissions are due. Obviously this can be flexible but to keep the process moving deadlines are good.
• Meetings: when and how should we meet to discuss? I personally am a big fan of Zoom for things like this. I have a professional account and would be happy to host an initial meeting to discuss ideas if others are interested. Beyond the initial meeting how should we continue meetings? biweekly, monthly, etc., 
• Tools: I am not sure what the rules are as far as creating and using tools such as Slack, scrum boards, etc. I personally would like to create and use a Slack channel for this group. Also, it would be good to have some kind of software that is available for driving the content creation. Maybe a scrum board is a bit much but something like Trello, or even Google docs would be good.

These are just a few thoughts, suggestions, and ideas to help get us started. 

Brian 

Bryan Duarte | software engineer

Arizona State University Computer Science Ph.D Student
IGERT Fellow
Alliance for Person-centered Accessible Technology
Center for Cognitive Ubiquitous Computing
Google Scholar Profile