On Sun, Aug 10, 2014 at 9:25 PM, differentreality wrote:

On Wed, Jul 16, 2014 at 7:58 AM, differentreality wrote:

...

On Mon, Jun 23, 2014 at 9:26 PM, differentreality wrote:

...

On Sun, Jun 22, 2014 at 9:46 PM, differentreality wrote:

...

On Jun 16, 2014 11:00 AM, "differentreality" wrote:

...

On Sun, Jun 8, 2014 at 5:41 PM, differentreality wrote:

...

On Sat, May 31, 2014 at 10:47 PM, differentreality wrote: > On Sat, May 24, 2014 at 10:30 AM, differentreality > wrote: >> On Sat, May 3, 2014 at 9:27 PM, differentreality >> wrote: >>> Hey all, >>> >>> I will be working (too) on OSEM for this GSOC. >>> >>> My project is about refactoring the user/person model and implementing roles. >>> My mentors are Ancor and Artem, and we are already in touch. >>> If everything goes smoothly with these changes, there might be some >>> time left for me to work on more stuff too. But let's see... >>> >>> As Christian mentioned, recently there were several changes implemented. >>> Most related bugs are fixed, and we are still working on what's left. >>> In addition, we are starting to write tests, and that hopefully will >>> attract more contributors too. >>> >>> For the user/person model part of my project, I will be changing stuff >>> that could affect the other two projects too, so I hope that all 3 >>> students we can be in touch and coordinate efforts on that. >>> >>> I will be soon making public details about the implementation of my >>> gsoc project. >>> As a conference organizer I do have some concrete ideas regarding how >>> we should change the user/person models and what kind of roles we >>> would need, but I have had some very interesting ideas coming from >>> other organizers, based on their needs for their conferences. >>> >>> OSEM is for everyone to use, not just for openSUSE Conference, but any >>> other conference or other event (smaller or bigger). As such, we want >>> to try and make OSEM a suitable tool for more people. >>> So any valuable input is more than welcome! >>> >>> Feel free to contact me directly via email or ping me on IRC, create a >>> new issue or comment on github, reply to this thread... Anything works >>> really :) >>> >>> And stay tuned for more news! >>> >>> Stella >> >> Hey all, >> >> a lot of changes happening to OSEM these days :) >> >> A feature for translation of OSEM was requested during oSC14 and >> that's what I was working on before GSOC coding period officially >> started as well as the first couple of days of this week. >> Translation files will be uploaded at https://www.transifex.com/projects/p/osem/ >> Transifex project automatically accepts anyone to join the team in >> order to start translating. >> There is, however, an issue with devise routing when using locales >> which I still haven't figured out, as well as implementing the >> translation to the models, for which I have already automatically >> produced a translation file. >> >> In the meantime I am working on the first part of my GSOC project, >> which is the user/person model refactoring. My approach is to make the >> person model per conference and keep the user model just for signing >> in to the application. >> >> That way, we can maintain the integrity of conference data as time >> goes by (considering that a person does not always have the same >> biography, not even the same name!) >> >> I am almost through making the necessary changes to the code and the database. >> >> What is left to do? >> I still need to adjust the information shown for each user and person >> so that it better depicts the new structure. Moreover I want to add >> the functionality of either importing latest profile to person model >> or create a new person only if something has changed. I assume people >> do not want to re-enter their personal details for every single >> conference (and the profile information, which is held in the person >> model, is mandatory for registering to a conference or submitting a >> proposal). And that's what I will be working on next week! >> >> Stella > > Hi! > > It has been a tricky week, half of which was occupied by an unresolved > debate [1] on the need of conference-specific user data, and the other > half by studying about openID implementation in rails. > > I seem to be on the right track of openID with the gem > open_id_authenticate and the development keeps going. > > Stella > > [1] https://github.com/openSUSE/osem/issues/22

Hey :)

I am finalizing openID feature, omni_auth gem turned out to be easy to use, it does require, though, that you sign up as developer with each provider you want to use.

Waiting to hear back from my mentor, Ancor, for next week.

Hi,

I have worked on the User/Person models merge. There are a couple of things to finalize along with any additional comments that might come up from my mentors.

In addition, I made some final touches to the openid feature too, which is progressing.

They shall both be finalized this coming week, hopefully.

Stella

Hi all,

OpenID is implemented in OSEM and some final checks and documentation are on their way.

The user/person merge is ready, pending review for its implementation.

It's been a pretty busy time, until we finalized the User/Person models merged properly so that it is both ready for use and existing installations can migrate all their existing data too.

We run into a database encoding issue too while trying to update our own existing data (https://github.com/openSUSE/osem/issues/278)

But that's all over now and we are good to go.

What's next? That's authorization. We are implementing new roles, we are defining roles with specific abilities and we are providing access only to authorized users to each page of OSEM. (If you are running the registration desk, for instance, you will no longer be able to change the settings of the conference or have access to the submitted proposals).

Discussion for some aspects of the implementation is still going on (https://github.com/openSUSE/osem/issues/23 - constructive comments always welcome!), but the work has already begun.

Since this feature essentially affects every single page of the application, a lot of other buggies come to light and get added in the 'issues' list :)

That said, we have prepared the fixes for several issues that came up with latest conferences using the app. (Got more? You know what to do...)

Stella

Stella

Hey all!

So the second part of the changes that are coming to OSEM is pretty huge, and the last weeks have been overloaded, to say the least.

The big thing we are doing has to do with role authorization and I am happy to able to breathe and say that it's almost done! It took a lot of time and effort to finalize the plan we wanted to follow, but here we are!

We are introducing rolify to handle roles for users and cancancan to handle the authorization. We are going to have some 'actionable' roles: Organizer, CfP, Info Desk, Volunteers Coordinator and each user, based on his/her role, will have (or not) access to the pages of the admin panel.

Organizers are able to assign (more) roles to users.

The hardest part has been rebasing all the time against all the new changes that are being introduced by others, due to the fact that my changes affect almost every part of the app.

The main functionality is basiclaly ready, but there is still a bit of work to come, before the feature can be safely merged. (Tomorrow's meeting will determine the load of that work!)

In the meantime, I have stumbled upon several underlying issues with the code, that needed to be fixed before implementing the authorization. And at the same time we are receiving a lot of feedback (and bug issues) from other people that use OSEM (without being OSEM contributors - and that makes all the difference).

Stay tuned for more awesome :)

Stella

Hi! As GSOC comes to an end, you can now find a looooot of new and awesome features added! The roles and authorization are now there. Organizers can add other organizers or cfp team members or info desk team people in a conference. All past admins/organizers are now organizers for all past conferences. For new conferences, you should expect to be an organizer (automatically) if you create a new conference. If you have a different role, other than organizer, for a conference, you will soon realize that the admin menu is customized to your role and you no longer have access to everything. Note: We are currently fixing an issue in the live instace we are running for openSUSE events and we should be up and running with the new features real soon! The work of course never ends :) Feel free to send us your ideas via email / mailing lists / github. Stella -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org