Wiki documentation party?

[ted....@gmail.com]

Anyone interested in having a documentation party where we meet for a couple of hours to organize, update, and edit the Wiki? That seemed to be recurring topic at the last monthly meeting.

I'm wondering if interested parties meet up for a couple of hours we could all knock out a lot of the updates the group has been discussing. I'm free evenings and weekends.

We should meet somewhere with Wifi. And beer.

[Boxcutter729]

That's a really great idea. At the last session we had 3 hours in which I was hoping to redo our whole build program page, get a new procedure outlined. We were too distracted to make that happen unfortunately. It would be nice to set aside some time just for that. Sit around a table with some laptops and food and get the whole thing straightened out. Do you have a venue/date in mind? I'm out next weekend (motorcycle lessons), but any other time.

[Andrew Kane]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

If the meeting is somewhere I can reach by bike from Richmond Beach,
and don't have to pay to be there, then I will go.

Otherwise, people who edit the wiki should please:

1) Discuss proposed (big) changes - not individual edits, but
large-scale structural or vision changes- either here, on IRC, or on a
special list to be created if necessary.

2) Use the Talk: pages, accessible on the tab labeled "Discussion" at
the upper-left corner of the relevant wiki page. This is a good place
to make note of proposed changes before you make them, or to talk
about the larger context of a series of smaller edits you're making,
or to explain why you've changed something that might be contentious.

3) Don't make monster edits. Adding a big block of text is fine, but
committing a bunch of additions, deletions and other changes all in
one edit is bad, because it makes difficulty in un-doing things. If
you make a monster edit and then want to roll back _part_ of it, you
then have to do it by hand- and the next item becomes impossible.

4) Use the history. If you are on fire to re-do something large and
complex (see item 5) but you don't have time to leave the page in a
good state, you can commit what changes you have time for and then
roll the page back to the state in which you found it. Then, when you
have time, you can merge your changes back in and continue.

5) If you're working on a large and complex page, and you didn't write
it yourself, keep in mind that it represents the effort of other
people. Don't chop things up willy-nilly, and use the "Summary:" field
on the Edit page to explain why you made each change. Even if no one
else actively works on the page, these blurbs will help you to
remember what you did and understand why you did it. Don't assume that
you'll be able to remember in two years why you made today's commits.
Ask Me How I Know ;^)

6) Before editing, please read this:
http://freegeekseattle.org/wiki/index.php/Help:Contents - Please note
that the "Help" link on the left-hand sidebar no longer points to our
Help: section. I've added a link on the Main page(under "About this
site"), and you can always use the URL above to get there manually.
I'll see if I can get the link fixed in the next month or so.

The wiki is most folks' first point of contact with Free Geek Seattle.
If it looks bad, we look bad. Please, let's make an effort to avoid
messing it up too much.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQEcBAEBAgAGBQJTjPXFAAoJEAa852fG4/6BHAsIAIWNpRWhtZGvKvAUveuv28/p
mFIIQiPIyiNqKHeh951vGEr6wM5NSLE5ARCw8msurITw5Kjkj6I/t2m1C4KBFFkA
cB7Xt16E/12KvKRaggID/UYUEmk8Gv1NnjjsYBt2D1d5/4tCCdZXIwtqNLvKx5Br
dFq9VZo5vuiVPU88i4oDWOdXHZj2IZMhvGouUHU8FfB/EW9yKf0Dw0W47sap3Lg5
Fp26fJXNqVyzHS6UYZCzuhdxlLrdT7tpTtKdVdaamV6abt2B3oRmyTarK+/LuG6L
E0jC+kbyUushuO4e19gKafPVxiUfR2gepS/47aY0I0vbcM1YdHDJb0eenjFrwC0=
=WdbP
-----END PGP SIGNATURE-----

[ted....@gmail.com]

How about Naked City Brewing? Great beer, lots of beer, tasty food, lots of tables, and WiFi.

https://nakedcitybrewing.com/

How does Saturday, June 21st sound? 11am?

On Saturday, May 31, 2014 1:04:05 PM UTC-7, ted....@gmail.com wrote:

[Tom Heuser]

I'm in.

Cura ut valeas!
-Tom Heuser

"Felix qui potuit rerum cognoscere causas" - Virgil

--
You received this message because you are subscribed to the Google Groups "freegeek-seattle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to freegeek-seatt...@googlegroups.com.
To post to this group, send email to freegeek...@googlegroups.com.
Visit this group at http://groups.google.com/group/freegeek-seattle.

[ted....@gmail.com]

Naked City opens at 11:30, so we'll have to change the time to then.

Are there any pages we should pay particular attention to?

[boxc...@freegeekseattle.org]

I'm in for next weekend with this.

[Blibbet]

> Are there any pages we should pay particular attention to?

‌
Yes. The page for the build/QA/assembly checklists. That is the main
page that matters for the weekly workshops.

Right now, we're still using Portland lists in the lab, which is crazy,
have of the answers to the kids in last few weeks was "no, they do that
in portland, i don't know why our docs are still that outdated, just
skip that section."

I seem to recall Andrew talking about a revised Seattle-based PDF, but
I haven't seen it and can't find it on the wiki.

Next weeks's workshop needs an up-to-date Seattle-based -- not
Portland-based -- checklist for the volunteers, multiple hardcopies of
it in the lab, one clipboard per copy per volunteer.

There is one hardcopy in the lab that has some hand-written
annotations, that should be used as a starting point. But it is the
only copy that the kids use, so if you take it, they'll be lost in the
lab.

[Boxcutter729]

This Saturday 11:30.

Naked City Brewey & Taphouse

8564 Greenwood Ave N

Seattle, WA 98103

I'll be there. Lets get this wiki down!

[Andrew Kane]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/14/2014 02:01 PM, ted....@gmail.com wrote:
> Naked City opens at 11:30, so we'll have to change the time to
> then.

Hi folks, I had meant to attend your shindig today but I'm not able to
get away. I hope some or all of you will sign into IRC while you're
doing your thing, so that others who can't make it can participate.

>
> Are there any pages we should pay particular attention to?

https://freegeekseattle.org/wiki/index.php?title=User:Themartianist&action=edit&redlink=1
is linked on the Main Page, but Tom has no information on his personal
page nor on the Main Page. I *strongly* suggest no posting of personal
information on the Main Page.

https://freegeekseattle.org/wiki/index.php/Wiki_Maintenance_Working_Group

Just made this page for you lot and anyone else who wiki-works at the
regular.

https://freegeekseattle.org/wiki/index.php/Category:Unfinished

These pages are not finished. Arguably no wiki article is ever
finished, but these are more unfinished than most.

Probably everyone who's on the Working Group should know what
Templates, Categories and Namespaces are.

https://www.mediawiki.org/wiki/Help:Namespaces

https://www.mediawiki.org/wiki/Help:Templates

https://www.mediawiki.org/wiki/Help:Categories

Speaking of Templates, we have a few and they are all uncategorized.

https://freegeekseattle.org/wiki/index.php/Special:UncategorizedTemplates

Do they need to be categorized? Will they still be visible on one page
if they are (of course, we can give something more than one category,
so they could share a Category:Templates I suppose)?

The Special pages are a good source of inspiration:

https://freegeekseattle.org/wiki/index.php/Special:SpecialPages

Particularly:

https://freegeekseattle.org/wiki/index.php/Special:PopularPages

ok, by now the meeting has already started... this took a lot longer
to write than I'd anticipated.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQEcBAEBAgAGBQJTpdMJAAoJEAa852fG4/6B2zEIAKYt/EE7IuC5smesK9beOz43
aYDx+hqAnQxoUFSfHeL+NKGhEYENKAKwlLkJQMhDo/o1+lfYBUoCy2uJ48E27pGz
QoZsr6TKqLxrNXIcZfJgJpnnv1mZu9t2v4e5wti6izQE2WRmr0eWh21UeUWeoMjw
T8G/RawClMkC5ClEGOibDJ3fNSfL+S54BqrYSqNsNbHlJkNHrhrkBIh4Nsa5qei5
NUooihjWyDvv9BxChJYAYPHodOdJmLnrYp441/GJA6KxOU7V6dT7tEOX/iEmLqXm
n3Hk7Lg9Byb69WyMzbY3cKVzP5vZdwfMHFnn9GxcKH6dUlMtb2KGqmiwjK0X/+U=
=0qI3
-----END PGP SIGNATURE-----

[ted....@gmail.com]

Elcaset: I'd like to link to your contact information on the front page under hardware donation. How would you prefer interested donors contact you?

On Saturday, May 31, 2014 1:04:05 PM UTC-7, ted....@gmail.com wrote:

[Tom Heuser]

Just in case anyone gets this during the meeting I think a general "Contact" section with everyone's contact info including name, email, volunteer role, and description would be good to have.

Cura ut valeas!
-Tom Heuser

"Felix qui potuit rerum cognoscere causas" - Virgil

--

[elcaseti .]

Ted,

For hardware donations, the best way to contact me is don...@freegeekseattle.org.

Thanks,

Elcaset

On Sat, Jun 21, 2014 at 12:26 PM, <ted....@gmail.com> wrote:

--

You received this message because you are subscribed to the Google Groups "freegeek-seattle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to freegeek-seatt...@googlegroups.com.
To post to this group, send email to freegeek...@googlegroups.com.
Visit this group at http://groups.google.com/group/freegeek-seattle.

--

Free Geek Seattle- Helping The Needy Get Nerdy
http://www.freegeekseattle.org/
https://groups.google.com/group/freegeek-seattle/topics?hl=en

[Andrew Kane]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/22/2014 03:30 PM, elcaseti . wrote:
> Ted,
>
> For hardware donations, the best way to contact me is
> don...@freegeekseattle.org.
>
> Thanks,
>
> Elcaset
>

I've made this change.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQEcBAEBAgAGBQJTp3kKAAoJEAa852fG4/6BR7kH/R3z46ahiZc5eArpxnMkacUP
qSvUhSG3mUI3p3G/UeFXyw+lUQg31AF5Vx3tx0h0Sf4RxlQHJKwXct6H2kEDZwrs
CbI3Epbd62CCzbJJQSWoQp54leD6vF6c3Tj7KIId6p50bXGhglroKPQBxEQwlVXn
1E29hyKvA5mAWInZldPVcZk3u5rESqXCfdkeuMKGM6AclICTTV8+1D15PV7AIh2T
xYlOYwJyljg6e7JWy0xb+vuyYKDW4K5aAvXSv08Edr0Nx286aYUcRVuc398BekYN
RINu/ygavX+buGJjxnjDye+9Vlv+T+6PYLDKB3ADryaXDKgsVhyenRU1mrDZejI=
=Wfjn
-----END PGP SIGNATURE-----

[elcaseti .]

Thanks, Andrew.

--
You received this message because you are subscribed to the Google Groups "freegeek-seattle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to freegeek-seatt...@googlegroups.com.
To post to this group, send email to freegeek...@googlegroups.com.
Visit this group at http://groups.google.com/group/freegeek-seattle.

[Boxcutter729]

So it was just the two of us. I managed to clean up the Build page a little, and revised the whole Safety Class page.

The rest of the pages still need some work. I'll go through them later along with Portland's and pick the best steps from both.

[elcaseti .]

"I'll go through them later along with Portland's and pick the best steps from both."  <---- sounds good.  Thanks.

On Mon, Jun 23, 2014 at 8:29 AM, Boxcutter729 <boxcut...@gmail.com> wrote:

So it was just the two of us. I managed to clean up the Build page a little, and revised the whole Safety Class page.

The rest of the pages still need some work. I'll go through them later along with Portland's and pick the best steps from both.

--

You received this message because you are subscribed to the Google Groups "freegeek-seattle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to freegeek-seatt...@googlegroups.com.
To post to this group, send email to freegeek...@googlegroups.com.
Visit this group at http://groups.google.com/group/freegeek-seattle.

[Andrew Kane]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Very cool. I'm glad you in particular are working on it, since you've
been the one mostly taking care of its implementation lately. Thanks
for all you do.

I hate to add even more to your list, but could you perhaps put your
plans for the FCS network up on the wiki for people to look at?
There's already a page for it:

https://freegeekseattle.org/wiki/index.php/FCS_Network

If it would be easier for you, maybe you could send me a copy of the
diagram you showed me a while back about your ideas, and I'll put it
on the wiki myself. It just seems like a good thing to have handy.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQEcBAEBAgAGBQJTqOpHAAoJEAa852fG4/6BFK4IAIobukY/2t8DvSMWQ84rZsFE
H4nmLLWMR2rd+2IFvLGjlCFFmkBf5qpz7MVg3PsC8I+TIBZfbaSsVM9mXkXrT/DD
/uKq3n6UbAwzKCTStQKdYStXGBP31eaN9g8HNIP+Ohk0Sa98Sxnb+GRI9BGb5NYs
9plw0ibM3ilJi1+4CSrfyK2KSE0NFzFV3fhoJ0d8KOHGpDOqh+ut+ce6SGHQ9uxh
1YCewA1kLR5YKlo/SEeUtZi4DQ8MwC8mdHdxJsdoFK9h9zmolZYB3z7w40IAE05V
UHH8GGxEa+lm/081qxjRb8L1pJaF2i5ZPHmJq2G8rCeyCeP51X4IVo/Pi0GUic8=
=AfgQ
-----END PGP SIGNATURE-----

[boxc...@freegeekseattle.org]

If we're still going forward with that, yeah totally.