On 09/04/2013 09:54 PM, Richard Brown wrote:

On 4 September 2013 14:15, Ancor Gonzalez Sosa <ancor@suse.de> wrote:

...

On 08/30/2013 02:38 AM, Robert Schweikert wrote:

...

Hi,

The meeting minutes from past Monday's board call have been posted to the wiki ( https://en.opensuse.org/openSUSE:Board_meeting#Meeting_2013-08-26 )

As usual, if you have any questions, comments or concerns please respond to this thread or send a message to the board mailing list. I read this in the minutes:

...

Number of bugs have hit those that were sponsored for oSC13, thus there is an additional delay in processing, sorry I'd be more than happy to help out if there are any bugs in the application. I am really not aware of any. I know there are many reimbursement requests with incomplete information that were rejected, but the application allows the TSP committee to decide what to do with them.

Again, if there is anything I can help with, let me know.

Regards. Hi Ancor,

'Bug' may have been the wrong word (though at the time was our understanding), 'issues' was certainly the case.

Stuff like the application allowing the process to continue to a very advanced stage with incomplete information certainly seemed buggy at the time' and certainly caused 'issues' for some of us who applied through the TSP - myself included

It's not a bug, is a feature :-) Seriously, it was intentional. One of the design goals of the application was to fully rely on the TSP Committee criteria, because they are the only people empowered to take decisions on what should be approved and what not. We didn't wanted the application to interfere or to take the power away from the Committee.

The apparent inability to edit/delete/reupload a signed confirmation after the initial upload also appears to be a problem, especially as those of us who were struck by the first issue now need to do just that in order to provide a signed confirmation with the complete information.

Obviously, this is not intuitive enough because most people got confused in this point. Currently, when the applicant modifies the reimbursement request and submits a new version, it needs to be approved again by the TSP Committee (because it has changed) and then accepted again by the applicant (because the TSP Committee can change things before approving it). Only in this moment (after the approval and before the acceptance), the applicant is allowed to substitute the old signed confirmation with a new one. So once again, is a feature (introduced to ensure the integrity of the process), but it's true that is a confusing feature.

Since the meeting we know the situation has progressed positively, the TSP committee is keeping us in the loop and singing your praises, I'm confident things will become much better in the future.

Sure. Things are smooth in the first try. :-)

Thanks for everything,

Richard

Regards.

...

-- Ancor González Sosa openSUSE Team at SUSE Linux GmbH

-- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org

-- Ancor González Sosa openSUSE Team at Suse Linux GmbH -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org