All, I'd like to nominate Harrison Grundy (aka astrodog) to join SAC.
He'll be joining initially as our liaison to marketing for the new website branding overhaul, and has a track record helping out in the past on various SAC issues, as well as professional sys admin experience.
We should probably formalize this, but I suggest for new members we simply nominate by existing member, and then give a period of time for anyone to voice an objection, 48 hours perhaps? Maybe I should make a motion about adopting this practice? Since we don't have it in place, then members should vote per normal motions.
On Wed, Feb 8, 2017 at 5:19 PM, Alex Mandel <tech_dev@wildintellect.com> wrote:
All, I'd like to nominate Harrison Grundy (aka astrodog) to join SAC.
He'll be joining initially as our liaison to marketing for the new website
branding overhaul, and has a track record helping out in the past on various
SAC issues, as well as professional sys admin experience.
We should probably formalize this, but I suggest for new members we simply
nominate by existing member, and then give a period of time for anyone to
voice an objection, 48 hours perhaps? Maybe I should make a motion about
adopting this practice? Since we don't have it in place, then members should
vote per normal motions.
In the absence of a Committee adopting different operating procedures,
I think that the default method is the general committee guidelines, http://wiki.osgeo.org/wiki/Committee_Guidelines (recently revised so
could look at previous versions as well). This is more or less how
most OSGeo projects operate so should be fairly familiar and straight
forward to many people.
On Wed, Feb 08, 2017 at 05:19:36PM -0800, Alex Mandel wrote:
All, I'd like to nominate Harrison Grundy (aka astrodog) to join SAC.
He'll be joining initially as our liaison to marketing for the new website
branding overhaul, and has a track record helping out in the past on various
SAC issues, as well as professional sys admin experience.
+1, SAC welcomes new forces !
Harrison, I hope you'll find all the info you need on the wiki
and will help improving that documentation if you don't
Searching for "Drupal" I found a few "upgrade plan" pages
which I put under the "Drupal" category. a 2017 version is
waiting for input
Not sure whether more formalization is required. Objections would typically not go through lists (at least I'd hope) but as an informal exchange between the nominator, nominee and the objector.
Best regards,
Arnulf
Am 09.02.2017 um 02:19 schrieb Alex Mandel:
All, I'd like to nominate Harrison Grundy (aka astrodog) to join SAC.
He'll be joining initially as our liaison to marketing for the new website branding overhaul, and has a track record helping out in the past on various SAC issues, as well as professional sys admin experience.
We should probably formalize this, but I suggest for new members we simply nominate by existing member, and then give a period of time for anyone to voice an objection, 48 hours perhaps? Maybe I should make a motion about adopting this practice? Since we don't have it in place, then members should vote per normal motions.
On 9 February 2017 at 10:16, Sandro Santilli <strk@kbt.io> wrote:
On Wed, Feb 08, 2017 at 05:19:36PM -0800, Alex Mandel wrote:
All, I'd like to nominate Harrison Grundy (aka astrodog) to join SAC.
He'll be joining initially as our liaison to marketing for the new website
branding overhaul, and has a track record helping out in the past on various
SAC issues, as well as professional sys admin experience.
Alex, what happened with this nomination ?
Did it pass ? If so, what are the next steps ?
I'm touching the ground as I'd like to see more sysadmin
work being conducted (mostly Wiki/LDAP integration) and
wondering if Harrison could also help with that
--strk;
On Wed, Feb 08, 2017 at 05:19:36PM -0800, Alex Mandel wrote:
All, I'd like to nominate Harrison Grundy (aka astrodog) to join SAC.
He'll be joining initially as our liaison to marketing for the new website
branding overhaul, and has a track record helping out in the past on various
SAC issues, as well as professional sys admin experience.
We should probably formalize this, but I suggest for new members we simply
nominate by existing member, and then give a period of time for anyone to
voice an objection, 48 hours perhaps? Maybe I should make a motion about
adopting this practice? Since we don't have it in place, then members should
vote per normal motions.
I assume the next steps involve a ritual with robes in a cave where we sacrifice livestock. At least, that's how every *other* sysadmin thing I've worked on went.
Harrison
On Mar 13, 2017, at 6:34 AM, Sandro Santilli <strk@kbt.io> wrote:
Alex, what happened with this nomination ?
Did it pass ? If so, what are the next steps ?
I'm touching the ground as I'd like to see more sysadmin
work being conducted (mostly Wiki/LDAP integration) and
wondering if Harrison could also help with that
--strk;
On Wed, Feb 08, 2017 at 05:19:36PM -0800, Alex Mandel wrote:
All, I'd like to nominate Harrison Grundy (aka astrodog) to join SAC.
He'll be joining initially as our liaison to marketing for the new website
branding overhaul, and has a track record helping out in the past on various
SAC issues, as well as professional sys admin experience.
We should probably formalize this, but I suggest for new members we simply
nominate by existing member, and then give a period of time for anyone to
voice an objection, 48 hours perhaps? Maybe I should make a motion about
adopting this practice? Since we don't have it in place, then members should
vote per normal motions.
On Mon, Mar 13, 2017 at 06:38:18AM -0600, Harrison Grundy wrote:
I assume the next steps involve a ritual with robes in a cave where we sacrifice livestock. At least, that's how every *other* sysadmin thing I've worked on went.
LOL
I expected a mail from Alex to draw conclusions of the vote, so
it can serve as a reference. Then I guess you'll want to add
your name and "focus" on the wiki page about SAC, and maybe
join #osgeo-sac and things like that (we need a formal welcome
pack here
--strk
Harrison
> On Mar 13, 2017, at 6:34 AM, Sandro Santilli <strk@kbt.io> wrote:
>
> Alex, what happened with this nomination ?
> Did it pass ? If so, what are the next steps ?
>
> I'm touching the ground as I'd like to see more sysadmin
> work being conducted (mostly Wiki/LDAP integration) and
> wondering if Harrison could also help with that
>
> --strk;
>
>> On Wed, Feb 08, 2017 at 05:19:36PM -0800, Alex Mandel wrote:
>> All, I'd like to nominate Harrison Grundy (aka astrodog) to join SAC.
>> He'll be joining initially as our liaison to marketing for the new website
>> branding overhaul, and has a track record helping out in the past on various
>> SAC issues, as well as professional sys admin experience.
>>
>> We should probably formalize this, but I suggest for new members we simply
>> nominate by existing member, and then give a period of time for anyone to
>> voice an objection, 48 hours perhaps? Maybe I should make a motion about
>> adopting this practice? Since we don't have it in place, then members should
>> vote per normal motions.
>>
>> Thanks,
>> Alex
Apologies, been really bad about keeping track of emails, filtering
system broke down for a week.
Yes based on all positive feedback from multiple members, Harrison is
now part of SAC.
Hopefully he has a report on the marketing proposal's technology
component for the website rebrand.
Thanks,
Alex
On 03/13/2017 07:02 AM, Sandro Santilli wrote:
On Mon, Mar 13, 2017 at 06:38:18AM -0600, Harrison Grundy wrote:
I assume the next steps involve a ritual with robes in a cave where we sacrifice livestock. At least, that's how every *other* sysadmin thing I've worked on went.
LOL
I expected a mail from Alex to draw conclusions of the vote, so
it can serve as a reference. Then I guess you'll want to add
your name and "focus" on the wiki page about SAC, and maybe
join #osgeo-sac and things like that (we need a formal welcome
pack here
--strk
Harrison
On Mar 13, 2017, at 6:34 AM, Sandro Santilli <strk@kbt.io> wrote:
Alex, what happened with this nomination ?
Did it pass ? If so, what are the next steps ?
I'm touching the ground as I'd like to see more sysadmin
work being conducted (mostly Wiki/LDAP integration) and
wondering if Harrison could also help with that
--strk;
On Wed, Feb 08, 2017 at 05:19:36PM -0800, Alex Mandel wrote:
All, I'd like to nominate Harrison Grundy (aka astrodog) to join SAC.
He'll be joining initially as our liaison to marketing for the new website
branding overhaul, and has a track record helping out in the past on various
SAC issues, as well as professional sys admin experience.
We should probably formalize this, but I suggest for new members we simply
nominate by existing member, and then give a period of time for anyone to
voice an objection, 48 hours perhaps? Maybe I should make a motion about
adopting this practice? Since we don't have it in place, then members should
vote per normal motions.
The final proposals were all either Drupal or Wordpress (sorry github fans). So we should be looking at a content migration - rather than an ‘upgrade plan’. Just waiting for contract stuff to be signed, then we can in the open more
···
On 14 March 2017 at 01:03, Sandro Santilli <strk@kbt.io> wrote:
On Mon, Mar 13, 2017 at 05:40:47PM -0700, Alex Mandel wrote:
Yes based on all positive feedback from multiple members, Harrison is
now part of SAC.
Hopefully he has a report on the marketing proposal’s technology
component for the website rebrand.
On Mon, Mar 20, 2017 at 09:49:27AM -0700, Jody Garnett wrote:
Thanks for volunteering Harrison
The final proposals were all either Drupal or Wordpress (sorry github
fans). So we should be looking at a content migration - rather than an
'upgrade plan'. Just waiting for contract stuff to be signed, then we can
in the open more
In case of Drupal it'll still be just an "upgrade plan", no ?
I think we all agreed on the marketing side that Wordpress would be
much much easier for most people than Drupal is. The selected vendor
has experience with automated migration tools between the two.
On Mon, Mar 20, 2017 at 9:54 AM, Sandro Santilli <strk@kbt.io> wrote:
On Mon, Mar 20, 2017 at 09:49:27AM -0700, Jody Garnett wrote:
Thanks for volunteering Harrison
The final proposals were all either Drupal or Wordpress (sorry github
fans). So we should be looking at a content migration - rather than an
'upgrade plan'. Just waiting for contract stuff to be signed, then we can
in the open more
In case of Drupal it'll still be just an "upgrade plan", no ?
Apologies, been really bad about keeping track of emails, filtering
system broke down for a week.
Yes based on all positive feedback from multiple members, Harrison is
now part of SAC.
Hopefully he has a report on the marketing proposal’s technology
component for the website rebrand.
Thanks,
Alex
On 03/13/2017 07:02 AM, Sandro Santilli wrote:
On Mon, Mar 13, 2017 at 06:38:18AM -0600, Harrison Grundy wrote:
I assume the next steps involve a ritual with robes in a cave where we sacrifice livestock. At least, that’s how every other sysadmin thing I’ve worked on went.
LOL
I expected a mail from Alex to draw conclusions of the vote, so
it can serve as a reference. Then I guess you’ll want to add
your name and “focus” on the wiki page about SAC, and maybe
join #osgeo-sac and things like that (we need a formal welcome
pack here
–strk
Harrison
On Mar 13, 2017, at 6:34 AM, Sandro Santilli <strk@kbt.io> wrote:
Alex, what happened with this nomination ?
Did it pass ? If so, what are the next steps ?
I’m touching the ground as I’d like to see more sysadmin
work being conducted (mostly Wiki/LDAP integration) and
wondering if Harrison could also help with that
–strk;
On Wed, Feb 08, 2017 at 05:19:36PM -0800, Alex Mandel wrote:
All, I’d like to nominate Harrison Grundy (aka astrodog) to join SAC.
He’ll be joining initially as our liaison to marketing for the new website
branding overhaul, and has a track record helping out in the past on various
SAC issues, as well as professional sys admin experience.
We should probably formalize this, but I suggest for new members we simply
nominate by existing member, and then give a period of time for anyone to
voice an objection, 48 hours perhaps? Maybe I should make a motion about
adopting this practice? Since we don’t have it in place, then members should
vote per normal motions.
