Changes between Version 1 and Version 2 of PscMeeting02-22-2007


Ignore:
Timestamp:
02/22/07 15:28:09 (18 years ago)
Author:
robertbray
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PscMeeting02-22-2007

    v1 v2  
    1919== Actions ==
    2020
     21 * (Bob) Compile updated CLA and post for feedback.
     22 * (Bob) Create single Drupal left nav menu (hack till we can create the tabbed nav we want)
     23 * (Jason) Attempt to import open defects and enhancements from !CollabNet data into Trac.
     24 * (Bob) Create Google Summer of Code Potential Projects Page.
     25 * (All) Review OSGeo Project Sponsorship info at: http://wiki.osgeo.org/index.php/Project_Sponsorship
    2126
    2227== Transcript ==
     28{{{
     29<rbray> Lets start, Paul can join in if/when he shows up.
     30<jasonbirch>    I had a nightmare last night about ADSK going to annual releases for MGE, and dropping support for MGOS. This is taking up way too much of my brainspace :) I think it was triggered by reading one of Dave's posts on the MGE support newsgroups.
     31<rbray> What post was that?
     32<rbray> Don't loose any sleep over it, we are in this for the long haul.
     33<Andy_Morsell>  I just read that post a few minutes ago. About WFS in Enterprise and it being broken but fixed in Open. And that there would be a release of MGE in mid 2007 with the fixes.
     34<rbray> I'll look later, let's get going with the meeting.
     35<rbray> I have got new content for the both the CLA to make it project specific and a Corporate CLA.
     36<rbray> I'll put those into PDF form and post for review soon.
     37<jasonbirch>    Short topic :)
     38<rbray> Unless there are questions, that was all I had on that one...
     39<rbray> Moving on. Drupal is giving me fits implementing my Navigation scheme. So...
     40<rbray> We have two choices (or maybe more)
     41<jasonbirch>    I know... we're moving to SharePoint :)
     42<rbray> yea thats it
     43<rbray> I think it would be easiest at this point to build on expandable menu down the left side.
     44<rbray> Until I figure out how to do what I wanted in the first place.
     45<rbray> Another choice is to do something like drupal.org, use tabs and remove the left nav. But that is more work and restructuring than I care to do at the moment.
     46<rbray> So any objections to one big expandable menu?
     47<jasonbirch>    Works for me.
     48<rbray> Ok, I can do that sometime this week/weekend.
     49<bdechant>      sounds fine
     50<jasonbirch>    Menus in Drupal are painful. Last time I did this, I made my own block and hand-coded it to build from various tags / content types. All of that's gone from my brain now though (over a year ago)
     51<rbray> Yea and that is what I will need to do in order to implement my original scheme.
     52<rbray> I'll get there eventually, but I don't have the cycles right now.
     53<rbray> So then trac should be integrated when I do the menus.
     54<rbray> If anyone has cycles it would be good to get the rest of the content on wik.osgeo.org moved to the trac wiki.
     55<jasonbirch>    How do we get accounts?
     56<jasonbirch>    I can look at moving some of the RFCs
     57<rbray> You should have it.
     58<rbray> Login to trac using the same credentials you use to login to the Drupal site.
     59<rbray> We opened the trac wiki up so that anyone in the LDAP can edit.
     60<jasonbirch>    How come there is a "Home" tab on the main site? :D
     61<rbray> Oops.
     62<rbray> Thats reminents of my hacking. I'll remove it.
     63<jasonbirch>    FramkW: does password reset work through Drupal?
     64<FrankW>        jasonbirch: no, i don't think so yet.
     65<FrankW>        I can manually reset passwords.
     66<rbray> There was the form that Shawn put together to do that. I think it still works.
     67<FrankW>        rbray: it wasn't working for me last I tried, and you need to know your password to change it (assuming it is the _ldap/ldap.php page).
     68<rbray> Yes it was this one: http://osgeo.org/_ldap/ldap.php.
     69<rbray> And you need to know your password.
     70<jasonbirch>    sounds like an infinite loop to me...
     71<rbray> It seems to sometimes work. Not the greatest solution I admit.
     72<rbray> Ok, shall we move on to defects?
     73<jasonbirch>    Sure
     74<rbray> So Jason took the defect XML from CollabNet and put it into an access database.
     75<rbray> Which was impressive BTW.
     76<rbray> But now what do we do with it?
     77<jasonbirch>    I can dump to web pages, or we could look at importing into Trac
     78<rbray> The import to trac will lose all history. Trac import is really weak.
     79<jasonbirch>    Not if you write directly to the data model...
     80<rbray> Well we could do that.
     81<jasonbirch>    I'm not sure how to do that without walking on the current tickets though.
     82<rbray> I have not looked yet, how many unresolved issues are in there.
     83<jasonbirch>    I don't know either
     84<jasonbirch>    I'd have to query for records where last status update wasn't resolved I guess
     85<rbray> YEs that would do it.
     86<rbray> I am guessing there is only 20 or so...
     87<jasonbirch>    Counting enhancements?
     88<rbray> Maybe I am dreaming.
     89-->|    pagameba (n=pagameba@gw.dmsolutions.ca) has joined #mapguide
     90<rbray> Maybe we should just import the open ones.
     91<pagameba>      sorry I'm late
     92<TomFukushima>  I think that there is about 20-30.
     93<pagameba>      did I miss anything important?
     94<rbray> Just gave you all the work of moving stuff on the wiki to Trac.
     95<rbray> :)
     96<pagameba>      lol
     97<jasonbirch>    not joking...
     98<jasonbirch>    :)
     99<pagameba>      doh
     100<jasonbirch>    OK, maybe a little bit.
     101<jasonbirch>    What does Trac use as a database currently, SQLite PostgreSQL or MySQL?
     102<rbray> I think it is using SQLite.
     103<jasonbirch>    Can I get a copy to play with?
     104<FrankW>        yes, sqlite, and I can provide the db.
     105<jasonbirch>    Thanks Frank...
     106<rbray> if you can import the open ones that would be great. I think it would be useful.
     107<jasonbirch>    me too. as long as we don't get too much activity, I may even be able to retain the issue IDs.
     108<rbray> That will be hard. Trac uses just a number. it was a MGxxx in PT
     109<jasonbirch>    Simple in FME or SSIS.
     110<jasonbirch>    Just strip the letters.
     111<FrankW>        jasonbirch: grab http://www.gdal.org/tmp/trac_mapguide.db.gz
     112<FrankW>        lol ... fme your ultimate RDMBS processing engine.
     113<jasonbirch>    Your site doesn't appear to pass the correct content-type for GZ :)
     114<rbray> Yea unless Trac wants them to be consecutive.
     115<jasonbirch>    I'll have to look at that.
     116<rbray> it maybe better to ignore the issue ID and let SQLite reassign them.
     117<rbray> That way there can be no conflict.
     118<jasonbirch>    ok. I'll leave the old ID in the description or something?
     119<rbray> Yea that would be fine.
     120<jasonbirch>    FrankW: Oh, the site passes the right content type; I forgot that browsers handle gz decompression natively.
     121<bdechant>      Thanks for doing this Jason.
     122<rbray> Ok cool. Let us know how it goes on the internals list.
     123<rbray> And yes a big round of thanks to Jason.
     124<jasonbirch>    No guarantees, but I'll give it my best shot.
     125<FrankW>        +1
     126<rbray> If you get something working maybe we can apply the same process to the FDO defects. Which would be even better.
     127<rbray> Maybe you can offer this to everyone migrating off CollabNet :)
     128<FrankW>        lol
     129<jasonbirch>    No **** way. the XML-> db translation is hard. :)
     130<rbray> yea I know. Just giving you trouble.
     131<rbray> Ok, next topic: Google Summer of Code.
     132<jasonbirch>    I see lots of benefits, but I also don't have coding the skills to mentor someone.
     133<rbray> I think finding mentors should not be hard.
     134<FrankW>        I believe OSGeo will establish a SoC Administor so projects wanting to participate would need to propose projects and mentors.
     135<rbray> So then what we need to do is come up with a lsit fo projects with mentors.
     136<jasonbirch>    That would be awesome. I want placemarks in multigeometry KML polygons, and Chris hasn't added that to his latest RFC :)
     137<FrankW>        PS. think something a student could reasonably accomplish in a summer.
     138<HarisK>        I am working on combining Open source Google WebToolkit with MapGuide OS, is this something suitable ?
     139<jasonbirch>    Accessing data stored in Google Base? :)
     140<FrankW>        HarisK: this sounds like it would be an attractive propect for approval by google.
     141<HarisK>        and if some mentoring is need I am willing to help in
     142<jasonbirch>    ew, it's Java... :)
     143<FrankW>        I'd add the student gets 4.5K US. This isn't terribly attractive to North american CS students, but might be more so in some other parts of the world.
     144<rbray> I can supply a mentor for something as well.
     145<jasonbirch>    Do we say what we want and then the students propose it, or do students get assigned to projects, or what?
     146<FrankW>        I think you propose projects and mentors first.
     147<rbray> I'll start a wiki page and we can all add to it. How does that sound for a start?
     148<jasonbirch>    Sounds great.
     149<FrankW>        +1
     150<rbray> That will make sure we all get access to the Trac wiki too!
     151<HarisK>        fine
     152<jasonbirch>    That database file is SQLite 2.1. I don't think I have the ability to write to that. Have to look for an OLEDB provider I guess.
     153<rbray> I'll send out the link later today. If you cannot login to the wiki, let me know and I'll send you the links to add yourself / check if you are in the LDAP already.
     154<rbray> I think the SQLite site has an ODBC driver for it.
     155<rbray> Anyone know when the deadline for the Google Summer of Code is?
     156<FrankW>        Not off hand.
     157<FrankW>        But I think you should aim for projects and mentors in about 3 weeks.
     158<rbray> March 5: Mentoring organizations can begin submitting applications to Google
     159<rbray> March 12: Mentoring organization application deadline
     160<rbray> March 14: List of accepted mentoring organizations published on code.google.com; student application period opens
     161<rbray> March 24: Student application deadline
     162<rbray> Sorry just found it.
     163<FrankW>        so we have to have projects proposed by the 12th? Whew!
     164<rbray> That is what it looks like. Here is the FAQ page I was reading: http://code.google.com/support/bin/answer.py?answer=60325&topic=10729
     165<sigq`> Title: Developer Knowledge Base - What is the program timeline? (at code.google.com)
     166<rbray> Ok that was all my topics. Anyone have other topics?
     167<jasonbirch>    This is cool. You have to click to display errors... http://maps.google.com/maps?f=q&hl=en&q=http://code.google.com/soc/soc_map.kml&ie=UTF8&z=2&ll=15.284185,-61.171875&spn=155.776464,326.953125&om=1
     168<sigq`> Title: Google Maps (at maps.google.com)
     169<jasonbirch>    no other topics...
     170<TomFukushima>  Oh, I added an item to the agenda
     171<TomFukushima>  Quick vote (I hope) on the new PSC page
     172<TomFukushima>  I added the section that we had discussed at the last PSC meeting.
     173<TomFukushima>  Agenda is here: http://wiki.osgeo.org/index.php/MapGuide_PSC_Meeting_02-22-2007
     174<sigq`> Title: MapGuide PSC Meeting 02-22-2007 - OSGEO (at wiki.osgeo.org)
     175<jasonbirch>    Remind me...
     176<rbray> Sorry I needed to refresh. Got it now.
     177<rbray> The issue is after an RFC is accepted how does it get changed if it needs to (probably due to implementation issues)?
     178<jasonbirch>    Right.
     179<TomFukushima>  Right. The section that was added is in the Agenda (it's short).
     180<jasonbirch>    I think that current wording covers that off well.
     181<Andy_Morsell>  That verbiage is fine with me.
     182<rbray> Not real clear when it is required though. I assume the same rules apply as apply to requiring an RFC in the first place?
     183<rbray> e.g. format changes from what is speced in the RFC?
     184<jasonbirch>    Gotta go. Sorry. Myu vote is +1
     185<rbray> or an API changes, or compatibilitiy will be affected in a different way?
     186|<--    jasonbirch has left irc.freenode.net ("Chatzilla 0.9.77 [Firefox 2.0.0.1/2006120418]")
     187<TomFukushima>  I would like it to be required for anything that an RFC is required for.
     188<rbray> If that is the intent, them I would motion to approve.
     189<bdechant>      +1
     190<rbray> OK, so then I'd like to Motion to approve the update.
     191<bdechant>      I second the motion and +1
     192<TomFukushima>  +1
     193<Andy_Morsell>  +1
     194<HarisK>        +1
     195<rbray> I am +1, so it is approved.
     196<rbray> Any other topics?
     197<Andy_Morsell>  We had a topic flying around this morning about donations for specific or general functionality enhancments. Is that worth talking about as a PSC and should we table that until the next meeting since we're out of time?
     198<rbray> Yes let's table that one for next meeting. We shoudl all take a look at the pages on sponsorship Frank mentioned in the e-mail.
     199<rbray> Ok then I motion to adjourn.
     200<rbray> Thanks everyone.
     201}}}