Cascadia programs for first year - Wikimedia-Cascadia

Pine W

18 Nov 18 Nov

11:13 a.m.

Thank you AB for commenting on Meta already (: I will explain here how I envision that our plan development process will work. Already done: Assemble a our Board; get consensus for creating a user group including its name and geographic scope; early program brainstorming and wishlisting; Affcom affiliation approval Step 1 (now): draft of program list with community input; finance and legal work in background; WMF trademark agreement Step 2: Board creation of bylaws and appointment of officers; Board selection of programs and calendar for programs; Board authorization to draft a budget and grant proposal; Board authorization to register Cascadia Wikimedians User Group as a nonprofit corporation with relevant government agencies; Board authorization to establish a registered agent and to create a bank account; Board authorization to seek a small "bridging the gap" grant for legal startup expenses like registered agent services prior to our Annual Plan grant; Board approval of trademark agreement with WMF Step 3: Budget and program plan/calendar draft development; obtain small grant for legal startup expenses and execute the funded tasks Step 4: Community review of budget and program plan/calendar Step 5: Board approval of.budget, program plan/calendar, and grant request(s) to fund the budget Step 6: Sumbit budget and grant proposal for review by grantmaker(s) Step 7: Recieve grant funding.and begin to execute programs (: After Step 7: quarterly Board reviews until it's time to create the next annual plan, with possible special meetings on occasion between regular quarterly meetings. Does that all sound ok? Any questions? Thanks, Pine On Nov 17, 2014 3:29 PM, "Pine W" <wiki.pine(a)gmail.com> wrote:

...

Hi all, I've put this on Meta: https://meta.wikimedia.org/wiki/Talk:Cascadia_Wikimedians#Drafting_programs… I'm hoping that people will comment so that we can get a sense about the priorities of our group. The Board can use the comments to finalize a program plan and an associated budget. The budget will be developed to support the program plan. I'm still working in the background about the "infrastructure" budget for issues like insurance, but even these will benefit greatly by being informed by a program plan. One important note is that the plan will likely be adjusted and adapted as our capabilities and opportunities change. My thinking is that the Board can do this via quarterly review meetings with community input. Please share your comments! Pine *This is an Encyclopedia* <https://www.wikipedia.org/> *One gateway to the wide garden of knowledge, where lies The deep rock of our past, in which we must delve The well of our future,The clear water we must leave untainted for those who come after us,The fertile earth, in which truth may grow in bright places, tended by many hands,And the broad fall of sunshine, warming our first steps toward knowing how much we do not know.* *—Catherine Munro*

Reply

Pine W

22 Nov 22 Nov

12:40 a.m.

Hi Jason, thanks for the info. Peaceray has followed up with some comments on Meta as well. It sounds like one thing that we have decided, in the usual wiki way of "someone should do X, no one else has stepped up to do it, and I can do it for the most part" is to create an *informal* communications primary contact list that goes something like this: University of Washington facilities/logistics: Mako Portland events, social media coordination, event calendar coordination, and mailing list administration: Jason GLAM: Peaceray Seattle events, and finance/grants/legal: Pine Is that all ok so far? It would be great if we got experienced, knowledgable and reliable contacts for event planning at WSU, British Columbia, and other locations. For the annual plan development timeline, I think we are likely to move to step 2 sometime in December or January. I am currenty woking really long days and something like 60 hours per week plus commute time. I hope that my workload will scale down to a more reasonable 50 hours per week in mid-December, so that I can do other projects including preparing for our first board meeting. One of the downsides of Cascadia's lack of paid staff and the reliance on volunteer time is that actions that would benefit Cascadia must wait until the volunteers can actually volunteer. We can add discussion of volunteer workload, availability, abilities, and risks of burnout to our list of factors for the Board to keep in mind during Annual Plan development. Right now, paid work must be my personal priority; I estimate that I top out at 2 hours per week for Cascadia volunteer work. I hope that everyone understands, and I appreciate your patience. In the meantime, everyone please do participate in the discussion on Meta. (: Regards, Pine Thank you for providing this timeline, Pine. I wouldn't mind if it were posted at Meta so we could keep track of our progress and use it as a checklist. As you acknowledged, I've responded with some program ideas at Meta. Throwing some spaghetti at the wall to see what sticks. Truly, our group will be much stronger if more people share their program priorities and wishes, so please take a look at the Meta discussion and add your thoughts. Also, you are welcome to update the "Possible calendar" section with dates for monthly meetups, possible monthly campaigns, one-offs like holiday parties, etc. I added the possibility of a Cascadia meetup at Wikimania 2015. There was not really a Cascadia meetup in London, but since the next conference is being held in North America there may be more Cascadian presence. Also, we can add WikiConference USA once the dates are set. Jason On Tue, Nov 18, 2014 at 1:13 AM, Pine W <wiki.pine(a)gmail.com> wrote:

...

Thank you AB for commenting on Meta already (: I will explain here how I envision that our plan development process will work. Already done: Assemble a our Board; get consensus for creating a user group including its name and geographic scope; early program brainstorming and wishlisting; Affcom affiliation approval Step 1 (now): draft of program list with community input; finance and legal work in background; WMF trademark agreement Step 2: Board creation of bylaws and appointment of officers; Board selection of programs and calendar for programs; Board authorization to draft a budget and grant proposal; Board authorization to register Cascadia Wikimedians User Group as a nonprofit corporation with relevant government agencies; Board authorization to establish a registered agent and to create a bank account; Board authorization to seek a small "bridging the gap" grant for legal startup expenses like registered agent services prior to our Annual Plan grant; Board approval of trademark agreement with WMF Step 3: Budget and program plan/calendar draft development; obtain small grant for legal startup expenses and execute the funded tasks Step 4: Community review of budget and program plan/calendar Step 5: Board approval of.budget, program plan/calendar, and grant request(s) to fund the budget Step 6: Sumbit budget and grant proposal for review by grantmaker(s) Step 7: Recieve grant funding.and begin to execute programs (: After Step 7: quarterly Board reviews until it's time to create the next annual plan, with possible special meetings on occasion between regular quarterly meetings. Does that all sound ok? Any questions? Thanks, Pine On Nov 17, 2014 3:29 PM, "Pine W" <wiki.pine(a)gmail.com> wrote:

Hi all, I've put this on Meta: https://meta.wikimedia.org/wiki/Talk:Cascadia_Wikimedians#Drafting_programs… I'm hoping that people will comment so that we can get a sense about the priorities of our group. The Board can use the comments to finalize a program plan and an associated budget. The budget will be developed to support the program plan. I'm still working in the background about the "infrastructure" budget for issues like insurance, but even these will benefit greatly by being informed by a program plan. One important note is that the plan will likely be adjusted and adapted as our capabilities and opportunities change. My thinking is that the Board can do this via quarterly review meetings with community input. Please share your comments! Pine *This is an Encyclopedia* <https://www.wikipedia.org/> *One gateway to the wide garden of knowledge, where lies The deep rock of our past, in which we must delve The well of our future,The clear water we must leave untainted for those who come after us,The fertile earth, in which truth may grow in bright places, tended by many hands,And the broad fall of sunshine, warming our first steps toward knowing how much we do not know.* *—Catherine Munro*

_______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

Reply

Jason Moore

23 Nov 23 Nov

4:32 a.m.

Pine, paid work should be your priority. Don't give yourself an ulcer working too hard on Cascadia-related work. Burnout is always a concern of mine for Wikipedia volunteers. I would recommend dedicating what time you can and ENJOY donating to the cause, because this group should be built out of love for the Wikimedia movement and for because it is something that brings a sense of mission and satisfaction. Again, if there are specific tasks you need done by volunteers, consider posting needs/requests here and/or at Meta-Wiki. Someone might be willing to raise their hand and assist with certain tasks. I am happy to help with Portland events and Cascadia social media when I can. I am trying to keep an eye on the mailing list (though not very successfully)... that is one task I would prefer to get off my plate when the group gets larger. It just is not on my radar and I am spread thin. I might also suggest that perhaps for our first year we base our program on existing campaigns and just trying to participate, and use the time to build our outreach strategies and communities. Events like Wiki Loves Monuments, Wiki Loves Libraries, Wiki Loves Pride, ArtAndFeminism, etc. already have established campaigns, press and best practices. Even if we simply hosted events in Cascadia as part of these larger campaigns, we would be doing good and building community. Let's not kill ourselves trying to do too much at once. I would rather we do less and improve our funding, social media and reporting channels. Build a solid foundation. Jason On Fri, Nov 21, 2014 at 3:57 PM, Raymond Leonard < raymond.f.leonard.jr(a)gmail.com> wrote:

...

I have somewhat busy end of year as well. I am running the Seattle Marathon on 11/30 (feel free to cheer on my bedraggled butt beyond the 20 mile marker) & away 12/24 through 12/27. I am on call 11/24-11/29, 12/6-12/14, & 12/22-12/23. Being on call does not necessarily mean that I cannot meet, but that my attendance may be preempted by work matters. I think that other than those days I can make a board meeting or two & some Wikimedia activities a priority in December. After Christmas, I should be pretty open except for 1/7-1/11 when my son visits. Many of us are busy at year's end, but I am providing my schedule so that maybe we can find a common puka <https://en.wiktionary.org/wiki/puka#Hawaiian> in our schedules that aligns. Maybe the weekend before Christmas or after New Year's, Public Domain Day <https://en.wikipedia.org/wiki/Public_Domain_Day>, or any evening that lines up. Yours, Peaceray On Fri, Nov 21, 2014 at 2:40 PM, Pine W <wiki.pine(a)gmail.com> wrote:

Hi Jason, thanks for the info. Peaceray has followed up with some comments on Meta as well. It sounds like one thing that we have decided, in the usual wiki way of "someone should do X, no one else has stepped up to do it, and I can do it for the most part" is to create an *informal* communications primary contact list that goes something like this: University of Washington facilities/logistics: Mako Portland events, social media coordination, event calendar coordination, and mailing list administration: Jason GLAM: Peaceray Seattle events, and finance/grants/legal: Pine Is that all ok so far? It would be great if we got experienced, knowledgable and reliable contacts for event planning at WSU, British Columbia, and other locations. For the annual plan development timeline, I think we are likely to move to step 2 sometime in December or January. I am currenty woking really long days and something like 60 hours per week plus commute time. I hope that my workload will scale down to a more reasonable 50 hours per week in mid-December, so that I can do other projects including preparing for our first board meeting. One of the downsides of Cascadia's lack of paid staff and the reliance on volunteer time is that actions that would benefit Cascadia must wait until the volunteers can actually volunteer. We can add discussion of volunteer workload, availability, abilities, and risks of burnout to our list of factors for the Board to keep in mind during Annual Plan development. Right now, paid work must be my personal priority; I estimate that I top out at 2 hours per week for Cascadia volunteer work. I hope that everyone understands, and I appreciate your patience. In the meantime, everyone please do participate in the discussion on Meta. (: Regards, Pine Thank you for providing this timeline, Pine. I wouldn't mind if it were posted at Meta so we could keep track of our progress and use it as a checklist. As you acknowledged, I've responded with some program ideas at Meta. Throwing some spaghetti at the wall to see what sticks. Truly, our group will be much stronger if more people share their program priorities and wishes, so please take a look at the Meta discussion and add your thoughts. Also, you are welcome to update the "Possible calendar" section with dates for monthly meetups, possible monthly campaigns, one-offs like holiday parties, etc. I added the possibility of a Cascadia meetup at Wikimania 2015. There was not really a Cascadia meetup in London, but since the next conference is being held in North America there may be more Cascadian presence. Also, we can add WikiConference USA once the dates are set. Jason On Tue, Nov 18, 2014 at 1:13 AM, Pine W <wiki.pine(a)gmail.com> wrote:

Thank you AB for commenting on Meta already (: I will explain here how I envision that our plan development process will work. Already done: Assemble a our Board; get consensus for creating a user group including its name and geographic scope; early program brainstorming and wishlisting; Affcom affiliation approval Step 1 (now): draft of program list with community input; finance and legal work in background; WMF trademark agreement Step 2: Board creation of bylaws and appointment of officers; Board selection of programs and calendar for programs; Board authorization to draft a budget and grant proposal; Board authorization to register Cascadia Wikimedians User Group as a nonprofit corporation with relevant government agencies; Board authorization to establish a registered agent and to create a bank account; Board authorization to seek a small "bridging the gap" grant for legal startup expenses like registered agent services prior to our Annual Plan grant; Board approval of trademark agreement with WMF Step 3: Budget and program plan/calendar draft development; obtain small grant for legal startup expenses and execute the funded tasks Step 4: Community review of budget and program plan/calendar Step 5: Board approval of.budget, program plan/calendar, and grant request(s) to fund the budget Step 6: Sumbit budget and grant proposal for review by grantmaker(s) Step 7: Recieve grant funding.and begin to execute programs (: After Step 7: quarterly Board reviews until it's time to create the next annual plan, with possible special meetings on occasion between regular quarterly meetings. Does that all sound ok? Any questions? Thanks, Pine On Nov 17, 2014 3:29 PM, "Pine W" <wiki.pine(a)gmail.com> wrote:

Hi all, I've put this on Meta: https://meta.wikimedia.org/wiki/Talk:Cascadia_Wikimedians#Drafting_programs… I'm hoping that people will comment so that we can get a sense about the priorities of our group. The Board can use the comments to finalize a program plan and an associated budget. The budget will be developed to support the program plan. I'm still working in the background about the "infrastructure" budget for issues like insurance, but even these will benefit greatly by being informed by a program plan. One important note is that the plan will likely be adjusted and adapted as our capabilities and opportunities change. My thinking is that the Board can do this via quarterly review meetings with community input. Please share your comments! Pine *This is an Encyclopedia* <https://www.wikipedia.org/> *One gateway to the wide garden of knowledge, where lies The deep rock of our past, in which we must delve The well of our future,The clear water we must leave untainted for those who come after us,The fertile earth, in which truth may grow in bright places, tended by many hands,And the broad fall of sunshine, warming our first steps toward knowing how much we do not know.* *—Catherine Munro*

_______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

_______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

_______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

Reply

Jon Beasley-Murray

11:50 p.m.

I am happy to help out with some organization in Vancouver, but can't put in masses of time. Take care Jon

...

On Nov 21, 2014, at 2:40 PM, Pine W <wiki.pine(a)gmail.com> wrote: Hi Jason, thanks for the info. Peaceray has followed up with some comments on Meta as well. It sounds like one thing that we have decided, in the usual wiki way of "someone should do X, no one else has stepped up to do it, and I can do it for the most part" is to create an *informal* communications primary contact list that goes something like this: University of Washington facilities/logistics: Mako Portland events, social media coordination, event calendar coordination, and mailing list administration: Jason GLAM: Peaceray Seattle events, and finance/grants/legal: Pine Is that all ok so far? It would be great if we got experienced, knowledgable and reliable contacts for event planning at WSU, British Columbia, and other locations. For the annual plan development timeline, I think we are likely to move to step 2 sometime in December or January. I am currenty woking really long days and something like 60 hours per week plus commute time. I hope that my workload will scale down to a more reasonable 50 hours per week in mid-December, so that I can do other projects including preparing for our first board meeting. One of the downsides of Cascadia's lack of paid staff and the reliance on volunteer time is that actions that would benefit Cascadia must wait until the volunteers can actually volunteer. We can add discussion of volunteer workload, availability, abilities, and risks of burnout to our list of factors for the Board to keep in mind during Annual Plan development. Right now, paid work must be my personal priority; I estimate that I top out at 2 hours per week for Cascadia volunteer work. I hope that everyone understands, and I appreciate your patience. In the meantime, everyone please do participate in the discussion on Meta. (: Regards, Pine Thank you for providing this timeline, Pine. I wouldn't mind if it were posted at Meta so we could keep track of our progress and use it as a checklist. As you acknowledged, I've responded with some program ideas at Meta. Throwing some spaghetti at the wall to see what sticks. Truly, our group will be much stronger if more people share their program priorities and wishes, so please take a look at the Meta discussion and add your thoughts. Also, you are welcome to update the "Possible calendar" section with dates for monthly meetups, possible monthly campaigns, one-offs like holiday parties, etc. I added the possibility of a Cascadia meetup at Wikimania 2015. There was not really a Cascadia meetup in London, but since the next conference is being held in North America there may be more Cascadian presence. Also, we can add WikiConference USA once the dates are set. Jason On Tue, Nov 18, 2014 at 1:13 AM, Pine W <wiki.pine(a)gmail.com> wrote: Thank you AB for commenting on Meta already (: I will explain here how I envision that our plan development process will work. Already done: Assemble a our Board; get consensus for creating a user group including its name and geographic scope; early program brainstorming and wishlisting; Affcom affiliation approval Step 1 (now): draft of program list with community input; finance and legal work in background; WMF trademark agreement Step 2: Board creation of bylaws and appointment of officers; Board selection of programs and calendar for programs; Board authorization to draft a budget and grant proposal; Board authorization to register Cascadia Wikimedians User Group as a nonprofit corporation with relevant government agencies; Board authorization to establish a registered agent and to create a bank account; Board authorization to seek a small "bridging the gap" grant for legal startup expenses like registered agent services prior to our Annual Plan grant; Board approval of trademark agreement with WMF Step 3: Budget and program plan/calendar draft development; obtain small grant for legal startup expenses and execute the funded tasks Step 4: Community review of budget and program plan/calendar Step 5: Board approval of.budget, program plan/calendar, and grant request(s) to fund the budget Step 6: Sumbit budget and grant proposal for review by grantmaker(s) Step 7: Recieve grant funding.and begin to execute programs (: After Step 7: quarterly Board reviews until it's time to create the next annual plan, with possible special meetings on occasion between regular quarterly meetings. Does that all sound ok? Any questions? Thanks, Pine On Nov 17, 2014 3:29 PM, "Pine W" <wiki.pine(a)gmail.com> wrote: Hi all, I've put this on Meta: https://meta.wikimedia.org/wiki/Talk:Cascadia_Wikimedians#Drafting_programs… I'm hoping that people will comment so that we can get a sense about the priorities of our group. The Board can use the comments to finalize a program plan and an associated budget. The budget will be developed to support the program plan. I'm still working in the background about the "infrastructure" budget for issues like insurance, but even these will benefit greatly by being informed by a program plan. One important note is that the plan will likely be adjusted and adapted as our capabilities and opportunities change. My thinking is that the Board can do this via quarterly review meetings with community input. Please share your comments! Pine This is an Encyclopedia One gateway to the wide garden of knowledge, where lies The deep rock of our past, in which we must delve The well of our future, The clear water we must leave untainted for those who come after us, The fertile earth, in which truth may grow in bright places, tended by many hands, And the broad fall of sunshine, warming our first steps toward knowing how much we do not know. —Catherine Munro _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

Reply

Jon Beasley-Murray

2:20 a.m.

BC. Take care Jon -- Jon Beasley-Murray University of British Columbia A short message, sent from my phone On Nov 28, 2014, at 4:18 PM, Pine W <wiki.pine(a)gmail.com> wrote:

...

Thanks for the comments, everyone. I'm way behind on email, apologizes for that. Jon, are you in Vancouver BC or Vancouver WA? Pine This is an Encyclopedia One gateway to the wide garden of knowledge, where lies The deep rock of our past, in which we must delve The well of our future, The clear water we must leave untainted for those who come after us, The fertile earth, in which truth may grow in bright places, tended by many hands, And the broad fall of sunshine, warming our first steps toward knowing how much we do not know. —Catherine Munro

On Mon, Nov 24, 2014 at 1:50 PM, Jon Beasley-Murray <jon.beasley-murray(a)ubc.ca> wrote: I am happy to help out with some organization in Vancouver, but can't put in masses of time. Take care Jon

On Nov 21, 2014, at 2:40 PM, Pine W <wiki.pine(a)gmail.com> wrote: Hi Jason, thanks for the info. Peaceray has followed up with some comments on Meta as well. It sounds like one thing that we have decided, in the usual wiki way of "someone should do X, no one else has stepped up to do it, and I can do it for the most part" is to create an *informal* communications primary contact list that goes something like this: University of Washington facilities/logistics: Mako Portland events, social media coordination, event calendar coordination, and mailing list administration: Jason GLAM: Peaceray Seattle events, and finance/grants/legal: Pine Is that all ok so far? It would be great if we got experienced, knowledgable and reliable contacts for event planning at WSU, British Columbia, and other locations. For the annual plan development timeline, I think we are likely to move to step 2 sometime in December or January. I am currenty woking really long days and something like 60 hours per week plus commute time. I hope that my workload will scale down to a more reasonable 50 hours per week in mid-December, so that I can do other projects including preparing for our first board meeting. One of the downsides of Cascadia's lack of paid staff and the reliance on volunteer time is that actions that would benefit Cascadia must wait until the volunteers can actually volunteer. We can add discussion of volunteer workload, availability, abilities, and risks of burnout to our list of factors for the Board to keep in mind during Annual Plan development. Right now, paid work must be my personal priority; I estimate that I top out at 2 hours per week for Cascadia volunteer work. I hope that everyone understands, and I appreciate your patience. In the meantime, everyone please do participate in the discussion on Meta. (: Regards, Pine Thank you for providing this timeline, Pine. I wouldn't mind if it were posted at Meta so we could keep track of our progress and use it as a checklist. As you acknowledged, I've responded with some program ideas at Meta. Throwing some spaghetti at the wall to see what sticks. Truly, our group will be much stronger if more people share their program priorities and wishes, so please take a look at the Meta discussion and add your thoughts. Also, you are welcome to update the "Possible calendar" section with dates for monthly meetups, possible monthly campaigns, one-offs like holiday parties, etc. I added the possibility of a Cascadia meetup at Wikimania 2015. There was not really a Cascadia meetup in London, but since the next conference is being held in North America there may be more Cascadian presence. Also, we can add WikiConference USA once the dates are set. Jason On Tue, Nov 18, 2014 at 1:13 AM, Pine W <wiki.pine(a)gmail.com> wrote: Thank you AB for commenting on Meta already (: I will explain here how I envision that our plan development process will work. Already done: Assemble a our Board; get consensus for creating a user group including its name and geographic scope; early program brainstorming and wishlisting; Affcom affiliation approval Step 1 (now): draft of program list with community input; finance and legal work in background; WMF trademark agreement Step 2: Board creation of bylaws and appointment of officers; Board selection of programs and calendar for programs; Board authorization to draft a budget and grant proposal; Board authorization to register Cascadia Wikimedians User Group as a nonprofit corporation with relevant government agencies; Board authorization to establish a registered agent and to create a bank account; Board authorization to seek a small "bridging the gap" grant for legal startup expenses like registered agent services prior to our Annual Plan grant; Board approval of trademark agreement with WMF Step 3: Budget and program plan/calendar draft development; obtain small grant for legal startup expenses and execute the funded tasks Step 4: Community review of budget and program plan/calendar Step 5: Board approval of.budget, program plan/calendar, and grant request(s) to fund the budget Step 6: Sumbit budget and grant proposal for review by grantmaker(s) Step 7: Recieve grant funding.and begin to execute programs (: After Step 7: quarterly Board reviews until it's time to create the next annual plan, with possible special meetings on occasion between regular quarterly meetings. Does that all sound ok? Any questions? Thanks, Pine On Nov 17, 2014 3:29 PM, "Pine W" <wiki.pine(a)gmail.com> wrote: Hi all, I've put this on Meta: https://meta.wikimedia.org/wiki/Talk:Cascadia_Wikimedians#Drafting_programs… I'm hoping that people will comment so that we can get a sense about the priorities of our group. The Board can use the comments to finalize a program plan and an associated budget. The budget will be developed to support the program plan. I'm still working in the background about the "infrastructure" budget for issues like insurance, but even these will benefit greatly by being informed by a program plan. One important note is that the plan will likely be adjusted and adapted as our capabilities and opportunities change. My thinking is that the Board can do this via quarterly review meetings with community input. Please share your comments! Pine This is an Encyclopedia One gateway to the wide garden of knowledge, where lies The deep rock of our past, in which we must delve The well of our future, The clear water we must leave untainted for those who come after us, The fertile earth, in which truth may grow in bright places, tended by many hands, And the broad fall of sunshine, warming our first steps toward knowing how much we do not know. —Catherine Munro _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

_______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

Reply

Pine W

11:28 a.m.

Hi Cascadians, Following up on the time requirements and my personal time budget: I spent about 8 hours today organizing, cleaning out, and following up on a month's worth of emails that had accumulated in my inbox. The clutter had grown to the point where I had trouble figuring out which emails were important. When I wasn't working 60 hour weeks, I could keep up with the email inflow. My situation has changed. I'm looking at the to-do list of things that need to happen to get CWUG well positioned to start executing programs, and I estimate that it would take me working alone about 40 hours to do a good job. Because my weekly availability is now relatively limited, that means it might take me many weeks to get through that list. I appreciate that other members of our group are willing to be patient. However, if anyone has spare time to do things like set up websites and bank accounts, please let me know. Otherwise, we'll probably continue to move along at a relatively slow pace, at least until I can take a few days of vacation from work and then sprint to wrap up a lot of projects. That will probably happen in January at the earliest, and February is more realistic. I admit that I'd rather spend a week of vacation in the mountains or in some tropical paradise! With this timing in mind, I think that having our first board meeting in January or February is likely. I'll probably continue to work on a slow pace leading up to the Board meeting, and then after the Board meeting I'll probably take a week's vacation from work and try to sprint through everything that needs to be done. I may ask the Board for some approvals prior to the Board meeting so that there can continue to be progress leading up to the board meeting. There are a variety of straightforward tasks that might be possible to do via email and wiki discussions. I think an in-person meeting will be very useful for complex decisions such as developing consensus about on the programs that we want to pursue in our first 6 to 12 months, authorizing bylaws, and selecting officers. I hope that all makes sense. I appreciate your patience. Pine *This is an Encyclopedia* <https://www.wikipedia.org/> *One gateway to the wide garden of knowledge, where lies The deep rock of our past, in which we must delve The well of our future,The clear water we must leave untainted for those who come after us,The fertile earth, in which truth may grow in bright places, tended by many hands,And the broad fall of sunshine, warming our first steps toward knowing how much we do not know.* *—Catherine Munro* On Fri, Nov 28, 2014 at 4:29 PM, Pine W <wiki.pine(a)gmail.com> wrote:

...

Jon, Excellent, we need a BC presence. In Seattle, simply having 2-hour unconference/social hangouts at coffee shops on a monthly basis near UW seems to work well for the purpose of keeping people connected and talking about projects. Would you be interested in holding similar events at UBC? Are there any programs that you think would be of most interest to students and faculty at UBC? Pine *This is an Encyclopedia* <https://www.wikipedia.org/> *One gateway to the wide garden of knowledge, where lies The deep rock of our past, in which we must delve The well of our future,The clear water we must leave untainted for those who come after us,The fertile earth, in which truth may grow in bright places, tended by many hands,And the broad fall of sunshine, warming our first steps toward knowing how much we do not know.* *—Catherine Munro* On Fri, Nov 28, 2014 at 4:20 PM, Jon Beasley-Murray < jon.beasley-murray(a)ubc.ca> wrote:

BC. Take care Jon -- Jon Beasley-Murray University of British Columbia A short message, sent from my phone On Nov 28, 2014, at 4:18 PM, Pine W <wiki.pine(a)gmail.com> wrote: Thanks for the comments, everyone. I'm way behind on email, apologizes for that. Jon, are you in Vancouver BC or Vancouver WA? Pine *This is an Encyclopedia* <https://www.wikipedia.org/> *One gateway to the wide garden of knowledge, where lies The deep rock of our past, in which we must delve The well of our future,The clear water we must leave untainted for those who come after us,The fertile earth, in which truth may grow in bright places, tended by many hands,And the broad fall of sunshine, warming our first steps toward knowing how much we do not know.* *—Catherine Munro* On Mon, Nov 24, 2014 at 1:50 PM, Jon Beasley-Murray < jon.beasley-murray(a)ubc.ca> wrote:

I am happy to help out with some organization in Vancouver, but can't put in masses of time. Take care Jon

On Nov 21, 2014, at 2:40 PM, Pine W <wiki.pine(a)gmail.com> wrote: Hi Jason, thanks for the info. Peaceray has followed up with some comments on Meta as well. It sounds like one thing that we have decided, in the usual wiki way

of "someone should do X, no one else has stepped up to do it, and I can do it for the most part" is to create an *informal* communications primary contact list that goes something like this:

University of Washington facilities/logistics: Mako Portland events, social media coordination, event calendar

coordination, and mailing list administration: Jason

GLAM: Peaceray Seattle events, and finance/grants/legal: Pine Is that all ok so far? It would be great if we got experienced, knowledgable and reliable

contacts for event planning at WSU, British Columbia, and other locations.

For the annual plan development timeline, I think we are likely to

move to step 2 sometime in December or January. I am currenty woking really long days and something like 60 hours per week plus commute time. I hope that my workload will scale down to a more reasonable 50 hours per week in mid-December, so that I can do other projects including preparing for our first board meeting. One of the downsides of Cascadia's lack of paid staff and the reliance on volunteer time is that actions that would benefit Cascadia must wait until the volunteers can actually volunteer. We can add discussion of volunteer workload, availability, abilities, and risks of burnout to our list of factors for the Board to keep in mind during Annual Plan development. Right now, paid work must be my personal priority; I estimate that I top out at 2 hours per week for Cascadia volunteer work. I hope that everyone understands, and I appreciate your patience. In the meantime, everyone please do participate in the discussion on Meta. (:

Regards, Pine Thank you for providing this timeline, Pine. I wouldn't mind if it

were posted at Meta so we could keep track of our progress and use it as a checklist.

As you acknowledged, I've responded with some program ideas at Meta.

Throwing some spaghetti at the wall to see what sticks. Truly, our group will be much stronger if more people share their program priorities and wishes, so please take a look at the Meta discussion and add your thoughts. Also, you are welcome to update the "Possible calendar" section with dates for monthly meetups, possible monthly campaigns, one-offs like holiday parties, etc. I added the possibility of a Cascadia meetup at Wikimania 2015. There was not really a Cascadia meetup in London, but since the next conference is being held in North America there may be more Cascadian presence. Also, we can add WikiConference USA once the dates are set.

Jason On Tue, Nov 18, 2014 at 1:13 AM, Pine W <wiki.pine(a)gmail.com> wrote: Thank you AB for commenting on Meta already (: I will explain here how I envision that our plan development process

will work.

Already done: Assemble a our Board; get consensus for creating a user

group including its name and geographic scope; early program brainstorming and wishlisting; Affcom affiliation approval

Step 1 (now): draft of program list with community input; finance and

legal work in background; WMF trademark agreement

Step 2: Board creation of bylaws and appointment of officers; Board

selection of programs and calendar for programs; Board authorization to draft a budget and grant proposal; Board authorization to register Cascadia Wikimedians User Group as a nonprofit corporation with relevant government agencies; Board authorization to establish a registered agent and to create a bank account; Board authorization to seek a small "bridging the gap" grant for legal startup expenses like registered agent services prior to our Annual Plan grant; Board approval of trademark agreement with WMF

Step 3: Budget and program plan/calendar draft development; obtain

small grant for legal startup expenses and execute the funded tasks

Step 4: Community review of budget and program plan/calendar Step 5: Board approval of.budget, program plan/calendar, and grant

request(s) to fund the budget

Step 6: Sumbit budget and grant proposal for review by grantmaker(s) Step 7: Recieve grant funding.and begin to execute programs (: After Step 7: quarterly Board reviews until it's time to create the

next annual plan, with possible special meetings on occasion between regular quarterly meetings.

Does that all sound ok? Any questions? Thanks, Pine On Nov 17, 2014 3:29 PM, "Pine W" <wiki.pine(a)gmail.com> wrote: Hi all, I've put this on Meta:

https://meta.wikimedia.org/wiki/Talk:Cascadia_Wikimedians#Drafting_programs…

I'm hoping that people will comment so that we can get a sense about

the priorities of our group. The Board can use the comments to finalize a program plan and an associated budget. The budget will be developed to support the program plan.

I'm still working in the background about the "infrastructure" budget

for issues like insurance, but even these will benefit greatly by being informed by a program plan.

One important note is that the plan will likely be adjusted and

adapted as our capabilities and opportunities change. My thinking is that the Board can do this via quarterly review meetings with community input.

Please share your comments! Pine This is an Encyclopedia One gateway to the wide garden of knowledge, where lies The deep rock of our past, in which we must delve The well of our future, The clear water we must leave untainted for those who come after us, The fertile earth, in which truth may grow in bright places, tended by

many hands,

And the broad fall of sunshine, warming our first steps toward knowing

how much we do not know.

—Catherine Munro _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

_______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

_______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

Reply

Jason Moore

1 Dec 1 Dec

5:47 p.m.

Another option is to create a Cascadia Wikimedians page at English Wikipedia. It might get more traffic and participation than the Meta pages. But, of course, this would just be one more page to manage. I would only recommend creating it if we think much of our activities will be centered around ENWP and if we think it would invite more participation. If we do want a page at ENWP (of course I am talking about a project page, not a Wikipedia article), I'd be happy to get one started. Jason On Sat, Nov 29, 2014 at 7:32 PM, Benj. Mako Hill <mako(a)atdot.cc> wrote:

...

Greetings Pine! <quote who="Pine W" date="Sat, Nov 29, 2014 at 01:28:10AM -0800">

However, if anyone has spare time to do things like set up websites and bank accounts, please let me know.

I'm happy to set up a website. What sort of thing were you thinking? It seems that lots of usergroups use their pages in meta as their main websites. Sometimes, groups have a prettier page on a domain that highlights some recent events and points there. I've hesitant to create a special website that we then need to maintain unless it's solving a problem. :) Later, Mako -- Benjamin Mako Hill http://mako.cc/ Creativity can be a social contribution, but only in so far as society is free to use the results. --GNU Manifesto _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

Reply

Jason Moore

6:38 p.m.

I have a thought, and with it comes a declaration of COI. Some of you may know that I work for the Internet registry for .wiki (among other top level domains). I don't know if it is required that we use a .org site (like most other Wikimedia affiliates), assuming we create an external site specifically for use by the group, but if we were interested in using something like cascadia.wiki we (group members) would not need to worry about registration, hosting, renewals and other maintenance requirements. I float this idea for several reasons: 1) Group members would have to accept using a .wiki domain. New TLDs are unfamiliar to some people, but I think a name like cascadia.wiki is unique, easy to read and remember, and intuitive, describing the region and the purpose of both the site and the group's activities. 2) To be upfront about my COI. Sure, I benefit indirectly from the domain's use in that awareness of the .wiki TLD benefits the company I work for, but really we are just talking about a single domain registration. We are not talking about lots of money here and I won't be getting any sort of bonus check for pitching a sale. Really, I just think it is a fantastic domain name and it would be great if more wiki projects took advantage of the .wiki option. 3) To make sure we consider all options and reduce overhead where we can. I just want to make this option known and offer to handle the relationship between the user group and the domain registry/registrar and hosting provider. I'd love to hear your thoughts and we can continue the discussion re: domain options at Meta if needed. Jason On Sat, Dec 6, 2014 at 4:10 PM, Pine W <wiki.pine(a)gmail.com> wrote:

...

I'm just now catching up on email. Regarding the website, I would like it to be a place where we can make our grants and board documents available. I feel that it should be legally separate from WMF web properties, although we may run MediaWiki on the website. The company that hosts the SeaFOSS website has provided me with good service and I'm planning to include a web hosting fee from them in our proposed budget and grant requests. I could run a site under my own name under my current contract, but it's legally preferable for our user group to have an independent contract. Once the website is operational I think the maintenance will be modest. We can continue to have discussions on Meta and have event postings also noted on Meta and ENWP. ENWP's geonotice feature is especially useful. I agree that we need to be mindful of maintenance requirements, and for that reason we might want to limit the content posted to our website while providing prominent referrals to places where we're already maintaining and updating information on Meta and English Wikipedia. I think the most labor-intensive part of the operation will be setting up the website; once that is done we'll probably only need to update it a few times a year. Mako and Jason, if you two would be willing to collaborate with each other to set up a modest website when we get the funds for hosting, I would appreciate it (: Pine *This is an Encyclopedia* <https://www.wikipedia.org/> *One gateway to the wide garden of knowledge, where lies The deep rock of our past, in which we must delve The well of our future,The clear water we must leave untainted for those who come after us,The fertile earth, in which truth may grow in bright places, tended by many hands,And the broad fall of sunshine, warming our first steps toward knowing how much we do not know.* *—Catherine Munro* On Mon, Dec 1, 2014 at 7:47 AM, Jason Moore <anotherbelieverwp(a)gmail.com> wrote:

Another option is to create a Cascadia Wikimedians page at English Wikipedia. It might get more traffic and participation than the Meta pages. But, of course, this would just be one more page to manage. I would only recommend creating it if we think much of our activities will be centered around ENWP and if we think it would invite more participation. If we do want a page at ENWP (of course I am talking about a project page, not a Wikipedia article), I'd be happy to get one started. Jason On Sat, Nov 29, 2014 at 7:32 PM, Benj. Mako Hill <mako(a)atdot.cc> wrote:

Greetings Pine! <quote who="Pine W" date="Sat, Nov 29, 2014 at 01:28:10AM -0800">

However, if anyone has spare time to do things like set up websites and bank accounts, please let me know.

I'm happy to set up a website. What sort of thing were you thinking? It seems that lots of usergroups use their pages in meta as their main websites. Sometimes, groups have a prettier page on a domain that highlights some recent events and points there. I've hesitant to create a special website that we then need to maintain unless it's solving a problem. :) Later, Mako -- Benjamin Mako Hill http://mako.cc/ Creativity can be a social contribution, but only in so far as society is free to use the results. --GNU Manifesto _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

_______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

Reply

Pine W

11:56 p.m.

I agree that in theory this could work. I'm with Mako in wondering about hosting in particular. The host for SeaFOSS is a bit more expensive than average but their service is very good, I've had a few interactions with their support staff and in every case I quickly got what I needed, and I think paying the price premium is worth the good service and maintainability. I am cautious about signing up with a host that might have a lower level of service quality that results in us spending hours of our valuable time trying to fix problems or make updates with inadequate support. Free hosting and registration sound good at first, but I feel that having quality hosting and maintainability are important, and I would want to investigate those issues before making a commitment to any host including a free host. So, AB, can you tell us more about how hosting would work? Thanks, Pine On Dec 7, 2014 9:14 AM, "Benj. Mako Hill" <mako(a)atdot.cc> wrote:

...

I don't know if it is required that we use a .org site (like most other Wikimedia affiliates), assuming we create an external site specifically for use by the group, but if we were interested in using something like cascadia.wiki we (group members) would not need to worry about registration, hosting, renewals and other maintenance requirements.

So, I love the idea of using cascadia.wiki for the group. At the very least, we could temporarliy just redirect somewhere else. I just did a search though and saw that it had already been registered. Was that one of us? Also, I don't understand how this gets off the hook for registration, hosting, renewels, etc? Later, Mako -- Benjamin Mako Hill http://mako.cc/ Creativity can be a social contribution, but only in so far as society is free to use the results. --GNU Manifesto _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

Reply

Benj. Mako Hill

1:35 a.m.

...

Cascadia.wiki is currently being reserved and could be made available at my request despite being considered a "premium" name.

Got it. :)

...

That being said, if the group is more comfortable with tasking someone to accept transfer of the domain and maintain hosting/renewals under his/her own name, we can help with those arrangements, too. I am not sure what additional detail is needed, but if you have specific questions or concerns, I'd be happy to respond.

I think that our long term plan should to have the domain ownership transfered to our organization. I don't mind if the technical contact, registration fees, and hosting is donated (in fact, that sounds wonderful!) but I think it is wise that our organization and its board have ownership and ultimate over the domain that people use to find us. Thank you so much for offering to organize this! Regards, Mako -- Benjamin Mako Hill http://mako.cc/ Creativity can be a social contribution, but only in so far as society is free to use the results. --GNU Manifesto

Reply

Pine W

10 Dec 10 Dec

2:02 a.m.

Hi, as of right now the board hasn't delegated any of its authority, which is an issue that will be addressed when we have bylaws so that a board vote isn't necessary for every decision. We may also pass some resolutions for temporary delegation of responsibility until the bylaws are finalized. For now, though, we'll need a board vote to approve obtaining property. Our Meta talk page would be a good place to do this for matters that aren't confidential. Jason, I suggest that you ask the relevant person in your org to draft a contract that specifies that Cascadia Wikimedians User Group will be donated ownership of the cascadia.wiki domain, and specifies how hosting arrangements and costs will be arranged (no cost is great), and the procedure for transferring hosting of the domain if we decide to host elsewhere. After we get a copyof the proposal, our board can review it, and discuss and vote on our Meta talk page. It would be nice if the agreement is produced under a Commons-compatible license so it can be reviewed by the public on Commons and potentially reused by others. Thanks! Pine On Dec 8, 2014 5:03 PM, "Jason Moore" <anotherbelieverwp(a)gmail.com> wrote:

...

And transferring ownership of the domain may be fine with the company, too. I'm not sure if/how domain registrations differ between individuals and organizations (not my area of expertise), but again I am happy to continue liaising between CWUG and the company and answer any specific questions re: registration and hosting. I've not heard any resistance to the domain cascadia.wiki for our group, so shall we continue moving forward with this plan or do we need to raise the question with other board members or at meta? Jason On Mon, Dec 8, 2014 at 3:35 PM, Benj. Mako Hill <mako(a)atdot.cc> wrote:

Cascadia.wiki is currently being reserved and could be made available

at my

request despite being considered a "premium" name.

Got it. :)

That being said, if the group is more comfortable with tasking someone to accept transfer of the domain and maintain hosting/renewals under his/her own name, we can help with those arrangements, too. I am not sure what additional detail is needed, but if you have specific questions or concerns, I'd be happy to respond.

I think that our long term plan should to have the domain ownership transfered to our organization. I don't mind if the technical contact, registration fees, and hosting is donated (in fact, that sounds wonderful!) but I think it is wise that our organization and its board have ownership and ultimate over the domain that people use to find us. Thank you so much for offering to organize this! Regards, Mako -- Benjamin Mako Hill http://mako.cc/ Creativity can be a social contribution, but only in so far as society is free to use the results. --GNU Manifesto

_______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

Reply

Lane Rasberry

4:59 a.m.

Hello, I support the use of a .wiki endorsement. I would support affiliation with Top Level Design, Jason's company, because I feel that anyone using wikis in any context is a benefit to the entire Wikimedia project, and because I feel like the favoritism given to the registrar for this domain is not significantly different as compared to favoritism given to someone doing a .com or .org registration. Also I feel that an affiliation with that company is an ideal partnership, because their very existence is premised on the past and future success of Wikimedia projects and the strength of any community groups in the region. Having a website off the Wikimedia projects might look professional but without multiple people to manage it then I am not convinced this is a priority. There is no Wikimedia group which has built community around their off-wiki website in the English language, and I doubt there is one at all. Off-wiki websites can be present past achieves to impress people who do project review, perhaps as part of a grant evaluation. Going off wiki typically means going off watchlists and out of touch with the Wikimedia community. In my opinion, staying in Wikimedia projects, perhaps with a .wiki redirect to a project page, is the most natural choice until there is a volunteer labor surplus and the organization navigates past its first cycle of grant requesting and reporting. Setting up a website achieves no stated early goal that I recognize. Content on Wikipedia could always be migrated to another website at a later time. yours, On Tue, Dec 9, 2014 at 7:02 PM, Pine W <wiki.pine(a)gmail.com> wrote:

...

Hi, as of right now the board hasn't delegated any of its authority, which is an issue that will be addressed when we have bylaws so that a board vote isn't necessary for every decision. We may also pass some resolutions for temporary delegation of responsibility until the bylaws are finalized. For now, though, we'll need a board vote to approve obtaining property. Our Meta talk page would be a good place to do this for matters that aren't confidential. Jason, I suggest that you ask the relevant person in your org to draft a contract that specifies that Cascadia Wikimedians User Group will be donated ownership of the cascadia.wiki domain, and specifies how hosting arrangements and costs will be arranged (no cost is great), and the procedure for transferring hosting of the domain if we decide to host elsewhere. After we get a copyof the proposal, our board can review it, and discuss and vote on our Meta talk page. It would be nice if the agreement is produced under a Commons-compatible license so it can be reviewed by the public on Commons and potentially reused by others. Thanks! Pine On Dec 8, 2014 5:03 PM, "Jason Moore" <anotherbelieverwp(a)gmail.com> wrote:

And transferring ownership of the domain may be fine with the company, too. I'm not sure if/how domain registrations differ between individuals and organizations (not my area of expertise), but again I am happy to continue liaising between CWUG and the company and answer any specific questions re: registration and hosting. I've not heard any resistance to the domain cascadia.wiki for our group, so shall we continue moving forward with this plan or do we need to raise the question with other board members or at meta? Jason On Mon, Dec 8, 2014 at 3:35 PM, Benj. Mako Hill <mako(a)atdot.cc> wrote:

Cascadia.wiki is currently being reserved and could be made available

at my

request despite being considered a "premium" name.

Got it. :)

That being said, if the group is more comfortable with tasking someone to accept transfer of the domain and maintain hosting/renewals under his/her own name, we can help with those arrangements, too. I am not sure what additional detail is needed, but if you have specific questions or concerns, I'd be happy to respond.

I think that our long term plan should to have the domain ownership transfered to our organization. I don't mind if the technical contact, registration fees, and hosting is donated (in fact, that sounds wonderful!) but I think it is wise that our organization and its board have ownership and ultimate over the domain that people use to find us. Thank you so much for offering to organize this! Regards, Mako -- Benjamin Mako Hill http://mako.cc/ Creativity can be a social contribution, but only in so far as society is free to use the results. --GNU Manifesto

_______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

-- Lane Rasberry user:bluerasberry on Wikipedia 206.801.0814 lane(a)bluerasberry.com

Reply

Jason Moore

8:01 a.m.

Thanks for your feedback, Lane and Peaceray. I do recognize Lane's concerns with moving outside of Meta and Wikipedia. Building a community at Cascadia.wiki and having to maintain the site will have its challenges. However, like Peacray mentioned, asking someone to visit Meta-Wiki and find the Cascadia Wikimedians page, or even asking someone to go to Wikipedia to find a theoretical project page for Cascadia Wikimedians has its own challenges. If we are to be seen as a group organizing "real life" activities and event, I think we need to have a website with the standard info we find online about other organizations: "about us", goals, bios for board members and volunteers/staff, calendar of upcoming events, grant requests and reports, contact info, etc.) Even if we organized our activities mostly using Meta-Wiki or English Wikipedia, I can still see benefits to having an external wiki... Possibly as an information/reporting repository moreso than a hub for organizing projects. Really, we would just have to see what happens organically. Having our own website will also mean we have the opportunity to brand ourselves a bit, to have a hub for social media links, signing up for an email mailing list, etc. Essentially, having an online presence and appearing more professional, like Lane mentioned. As for a redirect, I can speak with my colleagues, but I think it should not come as a surprise that a company donating a domain and hosting services might expect the domain to be used (I am speaking personally and independently of my employer). I'll try to start work on an agreement b/w TLD and WCUG, while also recognizing that this is an ongoing conversation re: both .wiki and even the use of an external website for the group. Jason On Tue, Dec 9, 2014 at 8:41 PM, Raymond Leonard < raymond.f.leonard.jr(a)gmail.com> wrote:

...

Hi everybody, I really like the idea of Cascadia.wiki. I agree with some of the sentiments about having it initially be a redirect to a Wikimedia project page even if we decide to eventually be separate from the WMF web properties. I think that the ability to tell people to go to Cascadia.wiki will be much simpler and so much more direct than having people go to meta.wikimedia.org then search for Cascadia Wikimedians or Wikimedia Cascadia. The casual user is probably unaware of meta.wikimedia.org; Cascadia.wiki is just easy to remember. I trust both Another Believer's / Jason's company & the company that hosts SeaFOSS on your (plural) recommendations. Thus, it seems to be basically a matter of logistics. I just think that we need to hash it out via a face-to-face whether that is in the same room or via Skype or Google Hangouts. Yours, Peaceray On Tue, Dec 9, 2014 at 6:59 PM, Lane Rasberry <lane(a)bluerasberry.com> wrote:

Hello, I support the use of a .wiki endorsement. I would support affiliation with Top Level Design, Jason's company, because I feel that anyone using wikis in any context is a benefit to the entire Wikimedia project, and because I feel like the favoritism given to the registrar for this domain is not significantly different as compared to favoritism given to someone doing a .com or .org registration. Also I feel that an affiliation with that company is an ideal partnership, because their very existence is premised on the past and future success of Wikimedia projects and the strength of any community groups in the region. Having a website off the Wikimedia projects might look professional but without multiple people to manage it then I am not convinced this is a priority. There is no Wikimedia group which has built community around their off-wiki website in the English language, and I doubt there is one at all. Off-wiki websites can be present past achieves to impress people who do project review, perhaps as part of a grant evaluation. Going off wiki typically means going off watchlists and out of touch with the Wikimedia community. In my opinion, staying in Wikimedia projects, perhaps with a .wiki redirect to a project page, is the most natural choice until there is a volunteer labor surplus and the organization navigates past its first cycle of grant requesting and reporting. Setting up a website achieves no stated early goal that I recognize. Content on Wikipedia could always be migrated to another website at a later time. yours, On Tue, Dec 9, 2014 at 7:02 PM, Pine W <wiki.pine(a)gmail.com> wrote:

Hi, as of right now the board hasn't delegated any of its authority, which is an issue that will be addressed when we have bylaws so that a board vote isn't necessary for every decision. We may also pass some resolutions for temporary delegation of responsibility until the bylaws are finalized. For now, though, we'll need a board vote to approve obtaining property. Our Meta talk page would be a good place to do this for matters that aren't confidential. Jason, I suggest that you ask the relevant person in your org to draft a contract that specifies that Cascadia Wikimedians User Group will be donated ownership of the cascadia.wiki domain, and specifies how hosting arrangements and costs will be arranged (no cost is great), and the procedure for transferring hosting of the domain if we decide to host elsewhere. After we get a copyof the proposal, our board can review it, and discuss and vote on our Meta talk page. It would be nice if the agreement is produced under a Commons-compatible license so it can be reviewed by the public on Commons and potentially reused by others. Thanks! Pine On Dec 8, 2014 5:03 PM, "Jason Moore" <anotherbelieverwp(a)gmail.com> wrote:

And transferring ownership of the domain may be fine with the company, too. I'm not sure if/how domain registrations differ between individuals and organizations (not my area of expertise), but again I am happy to continue liaising between CWUG and the company and answer any specific questions re: registration and hosting. I've not heard any resistance to the domain cascadia.wiki for our group, so shall we continue moving forward with this plan or do we need to raise the question with other board members or at meta? Jason On Mon, Dec 8, 2014 at 3:35 PM, Benj. Mako Hill <mako(a)atdot.cc> wrote: > > <quote who="Jason Moore" date="Mon, Dec 08, 2014 at 03:14:00PM -0800"> > > Cascadia.wiki is currently being reserved and could be made > available at my > > request despite being considered a "premium" name. > > Got it. :) > > > That being said, if the group is more comfortable with tasking > > someone to accept transfer of the domain and maintain > > hosting/renewals under his/her own name, we can help with those > > arrangements, too. I am not sure what additional detail is needed, > > but if you have specific questions or concerns, I'd be happy to > > respond. > > I think that our long term plan should to have the domain ownership > transfered to our organization. I don't mind if the technical contact, > registration fees, and hosting is donated (in fact, that sounds > wonderful!) but I think it is wise that our organization and its board > have ownership and ultimate over the domain that people use to find > us. > > Thank you so much for offering to organize this! > > Regards, > Mako > > > -- > Benjamin Mako Hill > http://mako.cc/ > > Creativity can be a social contribution, but only in so far > as society is free to use the results. --GNU Manifesto > _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

_______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

-- Lane Rasberry user:bluerasberry on Wikipedia 206.801.0814 lane(a)bluerasberry.com _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

_______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

Reply

Jason Moore

9:31 p.m.

Some feedback from Top Level Design: When ready, and with 30 days notice (for procedural purposes), CWUG should request the domain from TLD. TLD will transfer the domain, allowing CWUG to host as the group wishes. TLD can also provide hosting at no cost for one year. At any time after one year, TLD can request that the domain be transferred such that CWUG can take over both the domain and hosting. TLD is likely to continue hosting for a very long time, but the company should (understandably) have the right to no longer provide free hosting if it wishes (i.e., the arrangement is somehow problematic). I think this is very reasonable for both parties. It gives control of the domain to CWUG, allows free hosting for CWUG for a minimum of a year and possibly much longer, and allows CWUG to focus its efforts elsewhere. Even *IF* TLD decided to stop offering free hosting after a year (which I don't expect it will), all this would mean is that WCUG would need to subscribe to a hosting service with another company. Really, this is something that any group should expect to budget for anyway. But again, TLD would like to offer hosting for longer, but should have the right to back out if it wishes. Please don't interpret this as bait and switch or a free trial of sorts... I've been a part of the Wikimedia movement for 7 years and my boss has also been a long-time supporter of wiki communities. I assure you we are acting in good faith and just want to help, but I also recognize that both parties should be able to back out of the agreement if need be. The year clause seems appropriate for both parties, IMO. TLD would not place advertising on Cascadia.wiki, but it would be nice if the company were somehow recognized for its support, whether it be a link on the sidebar or another form of corporate recognition. (Again, this is something we should expect any contributing company to request.) For an example of a sidebar link, I share ICANNWiki and invite you to look at the bottom of the sidebar. Again, this is NOT required, or the wording can be changed, or whatever. Just sharing an example of what has worked elsewhere. Two more things: 1) TLD wants to know if CWUG is a legal entity and who the company would be making this agreement with specifically... in other words, who would the domain actually be transferred to? 2) Rather than drafting an extensive contract under a specific license, can I (on behalf of TLD) just outline the company's offer at Meta, which is public-facing and makes the company accountable for its actions? This to me seems better than spending a lot of time going back and forth drafting a contract. I don't think it needs to be so complicated. Thanks, and please feel free to voice your questions or concerns. Jason On Tue, Dec 9, 2014 at 11:21 PM, Pine W <wiki.pine(a)gmail.com> wrote:

...

Sounds good. I think I would advocate for more content than only a redirect. I think there should be a placeholder with contact info, and a link to meta. We can keep it simple and maintainable for now, with links to discussions on Meta. Perhaps we could eventually have the externally-oriented information like email signups, blogs and social media info on cascadia.wiki, while having relatively internal discussion on Meta? Jason, you're our social media person anyway, and if you want to maintain social media and communications info on cascadia.wiki, I think that might work well. Thanks a lot for working on this. Pine On Dec 9, 2014 10:24 PM, "Jason Moore" <anotherbelieverwp(a)gmail.com> wrote: > Thanks for your feedback, Lane and Peaceray. > > I do recognize Lane's concerns with moving outside of Meta and Wikipedia. > Building a community at Cascadia.wiki and having to maintain the site will > have its challenges. However, like Peacray mentioned, asking someone to > visit Meta-Wiki and find the Cascadia Wikimedians page, or even asking > someone to go to Wikipedia to find a theoretical project page for Cascadia > Wikimedians has its own challenges. > > If we are to be seen as a group organizing "real life" activities and > event, I think we need to have a website with the standard info we find > online about other organizations: "about us", goals, bios for board members > and volunteers/staff, calendar of upcoming events, grant requests and > reports, contact info, etc.) Even if we organized our activities mostly > using Meta-Wiki or English Wikipedia, I can still see benefits to having an > external wiki... Possibly as an information/reporting repository moreso > than a hub for organizing projects. Really, we would just have to see what > happens organically. > > Having our own website will also mean we have the opportunity to brand > ourselves a bit, to have a hub for social media links, signing up for an > email mailing list, etc. Essentially, having an online presence and > appearing more professional, like Lane mentioned. > > As for a redirect, I can speak with my colleagues, but I think it should > not come as a surprise that a company donating a domain and hosting > services might expect the domain to be used (I am speaking personally and > independently of my employer). I'll try to start work on an agreement b/w > TLD and WCUG, while also recognizing that this is an ongoing conversation > re: both .wiki and even the use of an external website for the group. > > Jason > > On Tue, Dec 9, 2014 at 8:41 PM, Raymond Leonard < > raymond.f.leonard.jr(a)gmail.com> wrote: > >> Hi everybody, >> >> I really like the idea of Cascadia.wiki. I agree with some of the >> sentiments about having it initially be a redirect to a Wikimedia project >> page even if we decide to eventually be separate from the WMF web >> properties. I think that the ability to tell people to go to Cascadia.wiki >> will be much simpler and so much more direct than having people go to >> meta.wikimedia.org then search for Cascadia Wikimedians or Wikimedia >> Cascadia. The casual user is probably unaware of meta.wikimedia.org; >> Cascadia.wiki is just easy to remember. >> >> I trust both Another Believer's / Jason's company & the company that >> hosts SeaFOSS on your (plural) recommendations. Thus, it seems to be >> basically a matter of logistics. I just think that we need to hash it out >> via a face-to-face whether that is in the same room or via Skype or Google >> Hangouts. >> >> Yours, >> Peaceray >> >> On Tue, Dec 9, 2014 at 6:59 PM, Lane Rasberry <lane(a)bluerasberry.com> >> wrote: >> >>> Hello, >>> >>> I support the use of a .wiki endorsement. I would support affiliation >>> with Top Level Design, Jason's company, because I feel that anyone using >>> wikis in any context is a benefit to the entire Wikimedia project, and >>> because I feel like the favoritism given to the registrar for this domain >>> is not significantly different as compared to favoritism given to someone >>> doing a .com or .org registration. Also I feel that an affiliation with >>> that company is an ideal partnership, because their very existence is >>> premised on the past and future success of Wikimedia projects and the >>> strength of any community groups in the region. >>> >>> Having a website off the Wikimedia projects might look professional but >>> without multiple people to manage it then I am not convinced this is a >>> priority. There is no Wikimedia group which has built community around >>> their off-wiki website in the English language, and I doubt there is one at >>> all. Off-wiki websites can be present past achieves to impress people who >>> do project review, perhaps as part of a grant evaluation. Going off wiki >>> typically means going off watchlists and out of touch with the Wikimedia >>> community. In my opinion, staying in Wikimedia projects, perhaps with a >>> .wiki redirect to a project page, is the most natural choice until there is >>> a volunteer labor surplus and the organization navigates past its first >>> cycle of grant requesting and reporting. Setting up a website achieves no >>> stated early goal that I recognize. Content on Wikipedia could always be >>> migrated to another website at a later time. >>> >>> yours, >>> >>> >>> >>> >>> >>> >>> >>> >>> On Tue, Dec 9, 2014 at 7:02 PM, Pine W <wiki.pine(a)gmail.com> wrote: >>> >>>> Hi, as of right now the board hasn't delegated any of its authority, >>>> which is an issue that will be addressed when we have bylaws so that a >>>> board vote isn't necessary for every decision. We may also pass some >>>> resolutions for temporary delegation of responsibility until the bylaws are >>>> finalized. For now, though, we'll need a board vote to approve obtaining >>>> property. Our Meta talk page would be a good place to do this for matters >>>> that aren't confidential. Jason, I suggest that you ask the relevant person >>>> in your org to draft a contract that specifies that Cascadia Wikimedians >>>> User Group will be donated ownership of the cascadia.wiki domain, and >>>> specifies how hosting arrangements and costs will be arranged (no cost is >>>> great), and the procedure for transferring hosting of the domain if we >>>> decide to host elsewhere. After we get a copyof the proposal, our board can >>>> review it, and discuss and vote on our Meta talk page. It would be nice if >>>> the agreement is produced under a Commons-compatible license so it can be >>>> reviewed by the public on Commons and potentially reused by others. >>>> >>>> Thanks! >>>> >>>> Pine >>>> On Dec 8, 2014 5:03 PM, "Jason Moore" <anotherbelieverwp(a)gmail.com> >>>> wrote: >>>> >>>>> And transferring ownership of the domain may be fine with the >>>>> company, too. I'm not sure if/how domain registrations differ between >>>>> individuals and organizations (not my area of expertise), but again I am >>>>> happy to continue liaising between CWUG and the company and answer any >>>>> specific questions re: registration and hosting. >>>>> >>>>> I've not heard any resistance to the domain cascadia.wiki for our >>>>> group, so shall we continue moving forward with this plan or do we need to >>>>> raise the question with other board members or at meta? >>>>> Jason >>>>> >>>>> On Mon, Dec 8, 2014 at 3:35 PM, Benj. Mako Hill <mako(a)atdot.cc> >>>>> wrote: >>>>> >>>>>> >>>>>> <quote who="Jason Moore" date="Mon, Dec 08, 2014 at 03:14:00PM >>>>>> -0800"> >>>>>> > Cascadia.wiki is currently being reserved and could be made >>>>>> available at my >>>>>> > request despite being considered a "premium" name. >>>>>> >>>>>> Got it. :) >>>>>> >>>>>> > That being said, if the group is more comfortable with tasking >>>>>> > someone to accept transfer of the domain and maintain >>>>>> > hosting/renewals under his/her own name, we can help with those >>>>>> > arrangements, too. I am not sure what additional detail is needed, >>>>>> > but if you have specific questions or concerns, I'd be happy to >>>>>> > respond. >>>>>> >>>>>> I think that our long term plan should to have the domain ownership >>>>>> transfered to our organization. I don't mind if the technical >>>>>> contact, >>>>>> registration fees, and hosting is donated (in fact, that sounds >>>>>> wonderful!) but I think it is wise that our organization and its >>>>>> board >>>>>> have ownership and ultimate over the domain that people use to find >>>>>> us. >>>>>> >>>>>> Thank you so much for offering to organize this! >>>>>> >>>>>> Regards, >>>>>> Mako >>>>>> >>>>>> >>>>>> -- >>>>>> Benjamin Mako Hill >>>>>> http://mako.cc/ >>>>>> >>>>>> Creativity can be a social contribution, but only in so far >>>>>> as society is free to use the results. --GNU Manifesto >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Wikimedia-Cascadia mailing list >>>>> Wikimedia-Cascadia(a)lists.wikimedia.org >>>>> https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia >>>>> >>>>> >>>> _______________________________________________ >>>> Wikimedia-Cascadia mailing list >>>> Wikimedia-Cascadia(a)lists.wikimedia.org >>>> https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia >>>> >>>> >>> >>> >>> -- >>> Lane Rasberry >>> user:bluerasberry on Wikipedia >>> 206.801.0814 >>> lane(a)bluerasberry.com >>> >>> _______________________________________________ >>> Wikimedia-Cascadia mailing list >>> Wikimedia-Cascadia(a)lists.wikimedia.org >>> https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia >>> >>> >> >> _______________________________________________ >> Wikimedia-Cascadia mailing list >> Wikimedia-Cascadia(a)lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia >> >> > > _______________________________________________ > Wikimedia-Cascadia mailing list > Wikimedia-Cascadia(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia > >

Reply

Pine W

14 Dec 14 Dec

9:47 a.m.

Hi, responding to a few points: *1) TLD wants to know if CWUG is a legal entity and who the company would be making this agreement with specifically... in other words, who would the domain actually be transferred to?* Response: Cascadia Wikimedians User Group is currently an unincorporated association. We are currently in the process of drafting bylaws and taking other steps to establish ourselves as a Washington State nonprofit corporation. The domain would become owned by CWUG, not by a single person. *2) Rather than drafting an extensive contract under a specific license, can I (on behalf of TLD) just outline the company's offer at Meta, which is public-facing and makes the company accountable for its actions? This to me seems better than spending a lot of time going back and forth drafting a contract. I don't think it needs to be so complicated.* Response: Yes, and what you've outlined in your email is OK. A contract can be short and to the point, and I think that what we have discussed here is sufficient basis for a contract. The only remaining steps are that CWUG's board needs to approve this agreement, and then indicate its readiness. We would need to work out the timing internally, for example by making sure that we have one or more people who are ready to put content on the site shortly after the domain is transferred. I anticipate that this will happen within the first half of 2015. *3) TLD would not place advertising on Cascadia.wiki, but it would be nice if the company were somehow recognized for its support, whether it be a link on the sidebar or another form of corporate recognition. (Again, this is something we should expect any contributing company to request.) For an example of a sidebar link, I share ICANNWiki and invite you to look at the bottom of the sidebar. Again, this is NOT required, or the wording can be changed, or whatever. Just sharing an example of what has worked elsewhere.* Response: I think we can work something out. I was imagining having a tastefully sized box somewhere on the homepage that says "Domain and hosting provided courtesy of TLD.com". If we put a list of other sponsors on the website homepage, we can include TLD in that list instead. Does this sound OK to you and the folks at TLD? Thanks! Pine

Reply

Pine W

10 Dec 10 Dec

8:13 a.m.

I'm happy to go with a zero-cost option for cascadia.wiki if that can be arranged and the terms are favorable, such as including a donation of the domain name and the option to move to a different host in the future. I think this could be considered plan A for now. Plan B is to host at the same host that SeaFOSS uses that, while of good quality, would involve financial expense. For the record, I paid for SeaFOSS hosting personally and have no relationship with the host outside of the services that I'm paying them to do. Also, I excluded web hosting from the draft startup budget that I recently posted on Meta because it seems to me that a website can wait until we develop our second (program-focused) budget. That's a good point about Cascadia.wiki being easier to remember than meta.wikimedia.org/wiki/Cascadia Wikimedians. I'm fine with the idea of a placeholder on cascadia.wiki until we agree that there's a benefit to putting more content on the site. Pine On Dec 9, 2014 8:41 PM, "Raymond Leonard" <raymond.f.leonard.jr(a)gmail.com> wrote:

...

Hi everybody, I really like the idea of Cascadia.wiki. I agree with some of the sentiments about having it initially be a redirect to a Wikimedia project page even if we decide to eventually be separate from the WMF web properties. I think that the ability to tell people to go to Cascadia.wiki will be much simpler and so much more direct than having people go to meta.wikimedia.org then search for Cascadia Wikimedians or Wikimedia Cascadia. The casual user is probably unaware of meta.wikimedia.org; Cascadia.wiki is just easy to remember. I trust both Another Believer's / Jason's company & the company that hosts SeaFOSS on your (plural) recommendations. Thus, it seems to be basically a matter of logistics. I just think that we need to hash it out via a face-to-face whether that is in the same room or via Skype or Google Hangouts. Yours, Peaceray On Tue, Dec 9, 2014 at 6:59 PM, Lane Rasberry <lane(a)bluerasberry.com> wrote:

Hello, I support the use of a .wiki endorsement. I would support affiliation with Top Level Design, Jason's company, because I feel that anyone using wikis in any context is a benefit to the entire Wikimedia project, and because I feel like the favoritism given to the registrar for this domain is not significantly different as compared to favoritism given to someone doing a .com or .org registration. Also I feel that an affiliation with that company is an ideal partnership, because their very existence is premised on the past and future success of Wikimedia projects and the strength of any community groups in the region. Having a website off the Wikimedia projects might look professional but without multiple people to manage it then I am not convinced this is a priority. There is no Wikimedia group which has built community around their off-wiki website in the English language, and I doubt there is one at all. Off-wiki websites can be present past achieves to impress people who do project review, perhaps as part of a grant evaluation. Going off wiki typically means going off watchlists and out of touch with the Wikimedia community. In my opinion, staying in Wikimedia projects, perhaps with a .wiki redirect to a project page, is the most natural choice until there is a volunteer labor surplus and the organization navigates past its first cycle of grant requesting and reporting. Setting up a website achieves no stated early goal that I recognize. Content on Wikipedia could always be migrated to another website at a later time. yours, On Tue, Dec 9, 2014 at 7:02 PM, Pine W <wiki.pine(a)gmail.com> wrote:

Hi, as of right now the board hasn't delegated any of its authority, which is an issue that will be addressed when we have bylaws so that a board vote isn't necessary for every decision. We may also pass some resolutions for temporary delegation of responsibility until the bylaws are finalized. For now, though, we'll need a board vote to approve obtaining property. Our Meta talk page would be a good place to do this for matters that aren't confidential. Jason, I suggest that you ask the relevant person in your org to draft a contract that specifies that Cascadia Wikimedians User Group will be donated ownership of the cascadia.wiki domain, and specifies how hosting arrangements and costs will be arranged (no cost is great), and the procedure for transferring hosting of the domain if we decide to host elsewhere. After we get a copyof the proposal, our board can review it, and discuss and vote on our Meta talk page. It would be nice if the agreement is produced under a Commons-compatible license so it can be reviewed by the public on Commons and potentially reused by others. Thanks! Pine On Dec 8, 2014 5:03 PM, "Jason Moore" <anotherbelieverwp(a)gmail.com> wrote:

And transferring ownership of the domain may be fine with the company, too. I'm not sure if/how domain registrations differ between individuals and organizations (not my area of expertise), but again I am happy to continue liaising between CWUG and the company and answer any specific questions re: registration and hosting. I've not heard any resistance to the domain cascadia.wiki for our group, so shall we continue moving forward with this plan or do we need to raise the question with other board members or at meta? Jason On Mon, Dec 8, 2014 at 3:35 PM, Benj. Mako Hill <mako(a)atdot.cc> wrote: > > <quote who="Jason Moore" date="Mon, Dec 08, 2014 at 03:14:00PM -0800"> > > Cascadia.wiki is currently being reserved and could be made > available at my > > request despite being considered a "premium" name. > > Got it. :) > > > That being said, if the group is more comfortable with tasking > > someone to accept transfer of the domain and maintain > > hosting/renewals under his/her own name, we can help with those > > arrangements, too. I am not sure what additional detail is needed, > > but if you have specific questions or concerns, I'd be happy to > > respond. > > I think that our long term plan should to have the domain ownership > transfered to our organization. I don't mind if the technical contact, > registration fees, and hosting is donated (in fact, that sounds > wonderful!) but I think it is wise that our organization and its board > have ownership and ultimate over the domain that people use to find > us. > > Thank you so much for offering to organize this! > > Regards, > Mako > > > -- > Benjamin Mako Hill > http://mako.cc/ > > Creativity can be a social contribution, but only in so far > as society is free to use the results. --GNU Manifesto > _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

_______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

-- Lane Rasberry user:bluerasberry on Wikipedia 206.801.0814 lane(a)bluerasberry.com _______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

_______________________________________________ Wikimedia-Cascadia mailing list Wikimedia-Cascadia(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimedia-cascadia

Reply