Re: Project Management update.

I think most people would assume the lifetime to be "for the session"
(meaning, until they close the browser).
(Unless you are using Chrome and then session cookies are kept, if I am not
mistaken)

☆*PhistucK*


On Mon, Feb 25, 2013 at 10:04 PM, Jonathan Garbee <jonathan@garbee.me>wrote:

> You can say how long a session cookie is good for. Depending on the system
> is is easily manipulated to boot. If MediaWiki or some other config in the
> system decides they should only be good for an hour or two, that is fine.
> I'm not sure how MW is setup by default in terms of session lifespan.
>
> For instance, with one system I use there is a simple configuration option
> I can use to set a number. That number denotes how many days the session
> cookie the software gives out is good for, I can also make them all (HTTPS
> or not) die on session exit by setting a 0. Same thing could apply to MW
> (and probably does.)
>
> I'll try to setup a MW install on a test VM in a day or two and have a
> look at the default config and see if there isn't an option to modify the
> lifetime.
>
> -Garbee
>
>
> On Mon, Feb 25, 2013 at 1:58 PM, PhistucK <phistuck@gmail.com> wrote:
>
>> A very low lifespan? is it not simply a session cookie?
>>
>> ☆*PhistucK*
>>
>>
>> On Mon, Feb 25, 2013 at 8:56 PM, Jonathan Garbee <jonathan@garbee.me>wrote:
>>
>>> The new system, I'll get the infrastructure project configured in about
>>> 15 minutes if it isn't already.
>>>
>>> Before filing again, do make sure that you are using the "remember me
>>> for 180 days" checkbox. If you don't then the cookie does have a very low
>>> lifespan. I think we actually should increase it to a few days.
>>>
>>> If there is something around not related to the actual lifetime of the
>>> cookie, then that is prime for reporting.
>>>
>>> Thanks,
>>> -Garbee
>>>
>>>
>>> On Mon, Feb 25, 2013 at 12:53 PM, Scott Rowe <scottrowe@google.com>wrote:
>>>
>>>> Hi Garbee,
>>>>
>>>> Apparently the infamous Session Bug somehow got closed in Bugzilla. But
>>>> it is still a big problem. I need to re-file two bugs related to this. Do I
>>>> use the new system or the old Bugzilla?
>>>>
>>>> +Scott
>>>>
>>>>
>>>>
>>>> On Wed, Feb 20, 2013 at 5:22 PM, Jonathan Garbee <jonathan@garbee.me>wrote:
>>>>
>>>>> The Content component import is finished! You should now be able to
>>>>> use the Content project [1] within the new solution to keep track of
>>>>> things. Once again, if you have any issues using the new install or have
>>>>> any questions, you can post them in the Project Management System project
>>>>> [2] or get in touch with me any other way you can and I can help you out.
>>>>>
>>>>> Some things are currently left in the component on Bugzilla. This is
>>>>> because they are going to be put into different projects which don't exist
>>>>> yet. So hang tight if you want to talk about one that is left sitting.
>>>>>
>>>>> -Garbee
>>>>>
>>>>> [1] http://project.webplatform.org/content
>>>>> [2] http://project.webplatform.org/prmg
>>>>>
>>>>>
>>>>> On Wed, Feb 20, 2013 at 3:38 PM, Eliot Graff <
>>>>> Eliot.Graff@microsoft.com> wrote:
>>>>>
>>>>>>  Thanks for the warning. ;-)****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> *From:* Jonathan Garbee [mailto:jonathan@garbee.me]
>>>>>> *Sent:* Wednesday, February 20, 2013 12:36 PM
>>>>>> *To:* public-webplatform@w3.org
>>>>>> *Subject:* Re: Project Management update.****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> In a few minutes I am going to begin importing the Content component
>>>>>> bugs from Bugzilla over to the new system. The way imports are going to
>>>>>> work is I will import and bring over the initial description of an issue.
>>>>>> If there are any other comments, I am going to do my best to bring the
>>>>>> content from them over as well (on some that may have a lot of
>>>>>> conversation, we will see. But I think most of those are resolved now.) As
>>>>>> the issues are ported over, I am going to close them as "RESOLVED" and
>>>>>> "MOVED" while also linking over to the new issue in our project management
>>>>>> system. ****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> So, to anyone who is signed up for the bugzilla mailing list, get
>>>>>> ready for inbox spamming! ;P****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> -Garbee****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> On Wed, Feb 20, 2013 at 7:18 AM, Jonathan Garbee <jonathan@garbee.me>
>>>>>> wrote:****
>>>>>>
>>>>>>  I think that is discussion for another thread/time. Right now it
>>>>>> really doesn't matter since our install doesn't work with OpenID.****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> On Wed, Feb 20, 2013 at 6:19 AM, PhistucK <phistuck@gmail.com> wrote:
>>>>>> ****
>>>>>>
>>>>>>  Once MediaWiki supports OpenID, I see no reason to have any other
>>>>>> login mechanism. We want to advocate open systems and secure practices,
>>>>>> which is what OpenID is about, unless I am mistaken.
>>>>>> ****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> ☆*PhistucK*****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> On Wed, Feb 20, 2013 at 1:15 PM, Jonathan Garbee <jonathan@garbee.me>
>>>>>> wrote:****
>>>>>>
>>>>>>  That has been planned. The module for it needs some patches before
>>>>>> we can use it. That is one of the bugs being imported into the new system.
>>>>>> ;)****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> It would only go one-way, so once we get support for having TBG talk
>>>>>> to the MW user base, we wouldn't use the OpenID system anymore since those
>>>>>> users wouldn't be in the MW DB. Unless, if people signed up through TBG it
>>>>>> would go into that DB, but I would be interested to see how that goes
>>>>>> seeing how TBG stores the OpenID data.****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> On Wed, Feb 20, 2013 at 6:07 AM, PhistucK <phistuck@gmail.com> wrote:
>>>>>> ****
>>>>>>
>>>>>>  And what about making MediaWiki have OpenID support?
>>>>>> ****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> ☆*PhistucK*****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> On Wed, Feb 20, 2013 at 12:15 PM, Jonathan Garbee <jonathan@garbee.me>
>>>>>> wrote:****
>>>>>>
>>>>>>  The system uses its own user DB. There is no module for letting it
>>>>>> work with a MediaWiki DB. It does have OpenID support, so this mitigates a
>>>>>> bit of the frustrations with needing another account. Getting it to work
>>>>>> with our current user DB is something to have done at some point.****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> -Garbee****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> On Wed, Feb 20, 2013 at 1:42 AM, PhistucK <phistuck@gmail.com> wrote:
>>>>>> ****
>>>>>>
>>>>>>  How do I log in?****
>>>>>>
>>>>>> My docs.webplatform.org username and password do not work. Is this
>>>>>> intentional? Will this be fixed?****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> Thank you for working on this!
>>>>>> ****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> ☆*PhistucK*****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> On Wed, Feb 20, 2013 at 12:35 AM, Jonathan Garbee <jonathan@garbee.me>
>>>>>> wrote:****
>>>>>>
>>>>>>  So, this is about to get inceptiony. Due to a bug in the current
>>>>>> ACL setup for TBG, the "General" settings actually don't work as they
>>>>>> should. :P So each project's permissions need to be manually set, which
>>>>>> makes creating them more time consuming then I originally estimated. It
>>>>>> won't be too bad though, just need to take them on one at a time compared
>>>>>> to rushing through creating them all at once as initially planned.***
>>>>>> *
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> Now, time for inception. I went ahead (completely without asking
>>>>>> anyone) and setup a project for tracking issues with the bug genie install
>>>>>> (yes, you can burn me at the stake for not asking, but let's do that after
>>>>>> it is all configured.) It is public and located here (
>>>>>> http://project.webplatform.org/prmg .) The "prmg" in the URL is for
>>>>>> "Project Management" and the actual title is "Project Management System."
>>>>>> So, for any issues or questions about using the system, just post in there.
>>>>>> There is one issue in particular currently which is about the import of the
>>>>>> current projects located here (
>>>>>> http://project.webplatform.org/prmg/issues/PRMG-2 .) It has the list
>>>>>> I am going to import the current projects in. Please comment if you have
>>>>>> any suggestions or problems with the import order.****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> Thanks,****
>>>>>>
>>>>>> -Garbee****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> On Tue, Feb 19, 2013 at 1:43 PM, Scott Rowe <scottrowe@google.com>
>>>>>> wrote:****
>>>>>>
>>>>>>  Looking good, Garbee!****
>>>>>>
>>>>>> +Scott****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> On Sat, Feb 16, 2013 at 4:19 PM, Jonathan Garbee <jonathan@garbee.me>
>>>>>> wrote:****
>>>>>>
>>>>>>  So, here we are. The Bug Genie is installed at
>>>>>> http://project.webplatform.org ! It is currently empty, so don't go
>>>>>> rushing over just yet. I'm finishing up a project that I have been caught
>>>>>> up in for about a month now within the next two days. So, Tuesday or
>>>>>> Wednesday will be when I begin configuring our TBG install. ****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> I'm estimating that should take me about two work days to get done
>>>>>> and test, perhaps three if I end up getting confused in the ACL (which is
>>>>>> pretty easy to do.) After that I will begin importing the issues from the
>>>>>> current Bugzilla repo into the new system. This will be done one component
>>>>>> per day to try and not burn myself out in the move and to try and do some
>>>>>> extra cleanup as well. As each component's move is completed I will update
>>>>>> the list to know to start using TBG for those issues. As far as the order
>>>>>> of the move, I will email out the order they will be done the day I start,
>>>>>> needless to say Content and Infrastructure are on the top of my list.
>>>>>> ****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> Probably the biggest question, support/documentation for TBG. This,
>>>>>> isn't a good answer I'm afraid. There is very little documentation on TBG's
>>>>>> actual usage. So at first, it really is just ask me any questions you have
>>>>>> via any method you can (coming to my house excluded, my dogs like to bark
>>>>>> at new visitors and it drives me nuts.) I will work on documenting the
>>>>>> actual usage of TBG first for us. Once that documentation is completed I
>>>>>> will work on documenting administration aspects of usage. ****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> If anyone has any specific questions about this process, please just
>>>>>> let me know. ****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> Thanks for your time,****
>>>>>>
>>>>>> -Garbee****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>>   ** **
>>>>>>
>>>>>>  ** **
>>>>>>
>>>>>>  ** **
>>>>>>
>>>>>>  ** **
>>>>>>
>>>>>>  ** **
>>>>>>
>>>>>>  ** **
>>>>>>
>>>>>>  ** **
>>>>>>
>>>>>>  ** **
>>>>>>
>>>>>>  ** **
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>