Tags are used to organize to-do pages on the wiki. The current tags are
a little confusing. I would like to rename two of them.
todo -> open
"todo" identifies open tasks. It would be clearer to just call it "open".
todo_issue -> todo
"todo_issue" identifies to-do pages. If "todo" gets renamed, this should
be renamed to "todo".
Also, I want to add a new tag:
This tag will identify tasks which are deemed important. What it says on
the tin. :-)
What do you folks think?
In past meetings people have emphasized the importance of having
pages for newcomers, outside observers and potential sponsors.
We also need to keep internal notes for people working on the
projects. Keeping these notes on the same pages intended for
newcomers would only confuse newcomers and would clutter the
notes intended for project participants.
I propose a project start page should give an overview. It is
for people not familiar with the project to learn what it is
about and how to participate. Internal administrative notes
should be on a separate admin page.
:start - describe the project, history, how it helps further
aw's goals, how to participate
:admin - administrative page, to-do list, notes on procedures
and common periodic tasks
classroom:start would be moved to classroom:admin.
mentorship:start and internships:start would stay where they are.
mentorship:admin and internships:admin would be created new.
How does that sound?
Those of us who spend much time on #archlinux-women, and other #archlinux channels, will have encountered phrik, the archlinux bot.
Many people are curious about him, so I thought I'd send some info to this list. phrik is a supybot. The Supybot handbook is at http://supybook.fealdia.org/devel/.
The next IRC meeting is on Sunday, April 5th at 16:00 UTC. A tentative agenda
can be found here: https://archwomen.org/wiki/meetings:2015_April
If there are topics you'd like to see on the agenda, please let us know or add
them to the wiki page. If you can't make the meeting, add a few comments in
the mailing list about any agenda item to be discussed in the meeting on
Sunday. As always, meeting notes and logs will be posted to the website and in
repositories on GitHub.