[Webcom] [OSGeo-Discuss] WebCom discussions

Ian Edwards iedwards.pub at gmail.com
Fri Sep 27 13:52:48 PDT 2013


agreed - we should keep implementation options open at this stage, I'm
equally happy with Django and I'll try to help with other options if
they're chosen.

I'll do some investigations into Drupal 8's multilingual support and see if
it supports the following requirement:
"We have to keep in mind that translation is being done by a growing bunch
of people who have little or no technical background. We need this to be
bullet proof and we need well defined processes on how to create
translations and whether or how to translate news / community spotlights,
etc." [1]

I'll report back on the WebCom list

[1] http://trac.osgeo.org/osgeo/ticket/202



On Fri, Sep 27, 2013 at 7:45 PM, Alex Mandel <tech_dev at wildintellect.com>wrote:

> Ian,
>
> That plan is I think the same conclusion I had reached. That some parts
> of the site simply need to be recoded, and I would open that it does not
> necessarily have to be drupal if we have experts in other platforms
> willing to jump in, things like the Service directory can easily be
> django or other platforms heavily used in the community.
>
> Our current goal, is to move the current site as is if possible over to
> the OSUOSL hosted machines. We hit a snag in PHP being too new for the
> older drupal and it broke some stuff. www.osgeo2.org  I think it is.
> If we can pull that off it would allow us to retire osgeo1 which is
> somewhat expensive to run, and would potentially free up funds to put
> towards re-coding of the site.
>
> FYI, if you feel Webcom needs a project management tool, how about a
> Trac instance?
>
> Thanks,
> Alex
>
>
> On 09/27/2013 03:31 AM, Ian Edwards wrote:
> > Thanks Alex, Frank. I'm happy to leave the project management tools
> > (basecamp) alone and lean more on SAC.  I'm also keen to make extensive
> use
> > of the wiki pages and to fill in missing documentation as we go.
> >
> > Looking through our custom Drupal modules I believe that we're unlikely
> to
> > find an upgrade path that will work - I suspect we're looking at a
> detailed
> > investigation of the functionality of the current site, followed by a
> > rebuild in Drupal 8 and automating the migration of content across.  We
> can
> > have several attempts at this in a development environment before
> > performing live migration tests and then making the decision to move
> across
> > to the new site when all of the requirements have been met.  Alex - I'm
> > very interested in hearing the thoughts of your Drupal colleague.  If he
> > agrees with this route then I think we should get started and we can use
> > WebCom to report regular progress on the specifics.
> >
> >
> >
> >
> >
> > On Thu, Sep 26, 2013 at 10:28 PM, Alex Mandel <
> tech_dev at wildintellect.com>wrote:
> >
> >> On 09/26/2013 02:10 PM, Frank Warmerdam wrote:
> >>> On Thu, Sep 26, 2013 at 2:04 PM, Alex Mandel <
> tech_dev at wildintellect.com
> >>> wrote:
> >>>
> >>>> On 09/26/2013 05:26 AM, Ian Edwards wrote:
> >>>>> To make more concrete progress on the larger issues facing WebCom I'd
> >>>> like
> >>>>> to start some closed discussions.
> >>>>>
> >>>>> If you have experience with the admin of any of the OSGeo
> >> infrastructure
> >>>>> then please join us.  We'll report back progress on the open WebCom
> >>>> mailing
> >>>>> list. Sensitive information about the systems will be thoroughly
> >>>> documented
> >>>>> and tested and will become a closed resource for the team moving
> >>>> forwards.
> >>>>>
> >>>>> Please reply off list and I'll add you to the discussion.
> >>>>>
> >>>>> Ian
> >>>>>
> >>>>>
> >>>>
> >>>> Webcom to my knowledge has been inactive for several years, are you
> the
> >>>> new Chair? The infrastructure you refer to has all been handled by
> >>>> members of the System Administration committee. Everything except
> >>>> security information (passwords) is publicly on the OSGeo Wiki if
> >>>> someone has taken the time to write it up.
> >>>>
> >>>
> >>> Alex,
> >>>
> >>> Webcom still notionally exists even if it is somewhat moribund.
> >>>
> >>> Ian has agreed to assist with the migration of Drupal, aspects of which
> >>> touch on SAC.
> >>>
> >>
> >> Excellent, I think it might be best to discuss how to get it done on the
> >> SAC list as Martin and I are the most familiar with the situation and
> >> have roughly attempted to do this task before getting distracted by
> >> other things (we can probably find old message thread for background).
> >> Once it's migrated I'm happy to let Webcom figure out what they want to
> >> change on a running site.
> >>
> >>> I don't think it would be all that helpful for Ian to struggle with
> >> whether
> >>> there ought to be a webcom, or if it is a SAC issue or a marketting
> >>> committee issue.
> >>>
> >>
> >> Agreed, revamp of the drupal site just needs to happen.
> >>
> >>> It is hopefully just about migrating Drupal and possibly doing some
> >> updates
> >>> to the web site - particularly as needed to make things work with a
> newer
> >>> drupal.
> >>>
> >>
> >> Right, I actually have someone who looked at it briefly (A drupal expert
> >> I work with), the trouble was we didn't have all the non-standard Drupal
> >> add-ons documented, so its hard to figure out how to keep them working
> >> right. If we feed him the right info, I can bug him to get it done or
> >> give us a quote if it'll cost some hours.
> >>
> >>> That said, I'm non-plussed by this idea of "closed" discussions and use
> >> of
> >>> some thing called basecamp.  Ian - why are closed discussions valuable
> >>> other than the need to be protective of a few passwords?
> >>>
> >>
> >> I agree, no need for basecamp (I do know what it is). We have a wiki and
> >> should use it.
> >>
> >>> Best regards,
> >>> Frank
> >>
> >> Thanks,
> >> Alex
> >>
>
>


More information about the Webcom mailing list