You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Tim Van Steenburgh <tv...@gmail.com> on 2013/02/01 00:26:06 UTC
Re: User stats and organizations
Hey guys,
I've started to look at this again. Getting several errors and failures running `nosetests` in ForgeUserStats. Can you look into that?
Tim
On Wednesday, January 30, 2013 at 2:17 PM, Tim Van Steenburgh wrote:
> Thanks guys! I'm in the middle of another code review at the moment, but I'll take a look soon.
>
> Tim
>
> On Wednesday, January 30, 2013 at 12:36 PM, Stefano Invernizzi wrote:
>
> > Dear Tim,
> > After fixing the issues you reported in your first review, we also fixed
> > other things today and we committed them to the repository.
> > We hope this improves our code. We also implemented the loop to register
> > additional listeners, as I had explained in the discussion of the ticket a
> > few days ago. Particularly, we forced the parameter in the configuration
> > file to be the equal to the entry point name, followed by ".enable", so
> > that the whole mechanism can be easily extended.
> > Let us know what you think about this additional commits and if there other
> > things to be improved. Thank you again for your review!
> >
> > Stefano & Simone
> >
> >
> > 2013/1/18 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)>
> >
> > > Stefano & Simone,
> > >
> > > I've posted a first review of the User stats code on
> > > https://sourceforge.net/p/allura/tickets/5453/.
> > >
> > > Tim Van Steenburgh
> > >
> > >
> > >
> > > On Wednesday, January 9, 2013 at 11:30 PM, Tim Van Steenburgh wrote:
> > >
> > > > Hi Stefano & Simone,
> > > >
> > > > Sorry for the delay, a lot of us were on extended vacation for the
> > > Christmas holiday. I've begun looking at your branch and intend to provide
> > > some feedback in the near future. Thanks for your contribution to Allura!
> > > >
> > > > Tim Van Steenburgh
> > > >
> > > >
> > > > On Wednesday, January 9, 2013 at 4:14 AM, Stefano Invernizzi wrote:
> > > >
> > > > > Dear all,
> > > > >
> > > > > We still didn't get any feedback about the uploaded code. Please, let
> > > us
> > > > > know what you think about it and if there's something we can improve.
> > > > >
> > > > > Regards,
> > > > >
> > > > > Simone & Stefano
> > > > >
> > > > >
> > > > > 2012/12/13 Stefano Invernizzi <stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com) (mailto:
> > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com))>
> > > > >
> > > > > > Dear all,
> > > > > > Since yesterday the code is available on the repository. As
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > suggested in
> > > > > > the proposed code contributors policy, I created a new branch named
> > > > > > si/5453. Feel free to comment our work, and send feedbacks or
> > > > > >
> > > > >
> > > >
> > >
> > > suggestions
> > > > > > about possible improvements.
> > > > > >
> > > > > > Stefano & Simone
> > > > > >
> > > > > >
> > > > > > 2012/12/11 Simone Gatti <simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com) (mailto:
> > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com))>
> > > > > >
> > > > > > > Dear all,
> > > > > > >
> > > > > > > thank you for your feedback!!
> > > > > > > First of all, in the next hours we'll create a branch with the
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > extension
> > > > > > > of
> > > > > > > UserStats, so that you can see our code to discuss it and its
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > possible
> > > > > > > improvements. After that we'll upload the extensions of the
> > > > > >
> > > > >
> > > >
> > >
> > > Organization
> > > > > > > and OrganizationStats.
> > > > > > > About the possibility to define an organization based on a shared
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > topic of
> > > > > > > interest, we have not considered it. We assumed that the kind of
> > > > > > > organization could be: "for-profit business", "foundation or other
> > > > > > > non-profit organization" or "research and/or education
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > institution", like
> > > > > > > the organizations in the real world. We don't know if the concept
> > > > > >
> > > > >
> > > >
> > >
> > > is the
> > > > > > > same, in that case we can easily add a new type of organization.
> > > > > > > (e.g."group of interest").
> > > > > > > As for Rich's proposal it's a great idea! We have considered it
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > but we
> > > > > > > later decided to focus on other aspects in our thesis. Anyway it's
> > > > > >
> > > > >
> > > >
> > >
> > > the
> > > > > > > best
> > > > > > > way to use the additional data included in the profile.
> > > > > > > I don't have commit access on the repository to upload my code.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > Since we
> > > > > > > developed it together, Stefano will commit it.
> > > > > > >
> > > > > > > Regards,
> > > > > > >
> > > > > > > Simone.
> > > > > > >
> > > > > > >
> > > > > > > 2012/12/10 Alvaro del Castillo <acs@bitergia.com (mailto:acs@bitergia.com) (mailto:
> > > acs@bitergia.com (mailto:acs@bitergia.com))>
> > > > > > >
> > > > > > > > Dear Simone,
> > > > > > > >
> > > > > > > > First of all, I am sorry about the delayed response.
> > > > > > > >
> > > > > > > > El jue, 29-11-2012 a las 19:06 +0100, Simone Gatti escribió:
> > > > > > > > > Dear all,
> > > > > > > > >
> > > > > > > > > During the last weeks, while discussing our work on including
> > > new
> > > > > > > details
> > > > > > > > > in users' profiles on the forge, I and Stefano Invernizzi also
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > continued
> > > > > > > > > working on the other features we introduced in one of our first
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > messages
> > > > > > > > on
> > > > > > > > > the mailing list, back in July.
> > > > > > > > > Now we have completed the implementation of these tools, and
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > we would
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > like
> > > > > > > > > to get feedbacks from you in order to check if it's possible to
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > include
> > > > > > > > > them on the Allura platform.
> > > > > > > > >
> > > > > > > > > The additional features we implemented consist of two main
> > > parts.
> > > > > > > First
> > > > > > > > of
> > > > > > > > > all, we included the concept of organization, namely companies,
> > > > > > > >
> > > > > > > >
> > > > > > > > foundations
> > > > > > > > > or other non-profit organizations and research and education
> > > > > > > >
> > > > > > > >
> > > > > > > > institutions.
> > > > > > > > > Each organization is now allowed to create a profile,
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > including some
> > > > > > > > > details about it, like a description, its working fields, its
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > size,
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > etc...
> > > > > > > > > . Moreover, users can be linked to the organizations they
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > belong to,
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > and
> > > > > > > > > projects can be linked to the organizations developing them.
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > For both
> > > > > > > >
> > > > > > > > these
> > > > > > > > > kinds of relationships, we implemented a two-way mechanism:
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > the user
> > > > > > > > > requests to be registered as a member of the organization and
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > the
> > > > > > > > > organization has to confirm it, or vice-versa. Similarly, an
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > organization
> > > > > > > > > sends a request to be listed as the developer of a project,
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > and the
> > > > > > > > > administrator of the project has to accept it, or vice-versa.
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > When a
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > user
> > > > > > > > > leaves an organization, he can set this on the forge, and the
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > enrollment
> > > > > > > > in
> > > > > > > > > this organization will be shown as a past membership. The same
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > applies
> > > > > > > >
> > > > > > > > for
> > > > > > > > > project collaborations: an organization can freely set a
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > collaboration
> > > > > > > > > within a project as completed, because the organization
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > doesn't want
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > to
> > > > > > > > > continue working on the project, and it will be shown as a past
> > > > > > > >
> > > > > > > >
> > > > > > > > involvement.
> > > > > > > > > We believe this features could be very useful on a forge which
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > is
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > used by
> > > > > > > > > more than one organization, because it allows to have a better
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > awareness
> > > > > > > > of
> > > > > > > > > the community, knowing how users working on a project are
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > organized in
> > > > > > > >
> > > > > > > > the
> > > > > > > > > real life. It can also increase trust for those projects
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > developed by
> > > > > > > > > well-known organizations.
> > > > > > > > >
> > > > > > > > > The second feature we developed is related to users, and
> > > consits of a
> > > > > > > set
> > > > > > > > > of metrics gathered from their activity.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > This is a really interesting thing for me!
> > > > > > > >
> > > > > > > > > These metrics include the number
> > > > > > > > > of created or modified artifacts (also separated for different
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > kinds
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > of
> > > > > > > > > artifacts), the number of assigned tickets, solved tickets and
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > "revoked"
> > > > > > > > > tickets, namely tickets which were assigned to a user but
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > whose owner
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > was
> > > > > > > > > later changed. Moreover, the number of commits is collected,
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > together
> > > > > > > >
> > > > > > > > with
> > > > > > > > > the total number of added or modified lines of code by the
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > user. For a
> > > > > > > > > certain user, all these metrics are shown on a page on the
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > form, as a
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > total
> > > > > > > > > value since the user's registration, as well as an average
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > per-month
> > > > > > > >
> > > > > > > > value.
> > > > > > > > > The metrics are also calculated considering the last 30 days
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > only, in
> > > > > > > >
> > > > > > > > order
> > > > > > > > > to allow to check whether the user is still active on the
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > forge or
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > not,
> > > > > > > > and
> > > > > > > > > if he is increasing his efforts on the forge or not.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Is this code already available?
> > > > > > > >
> > > > > > > > In Bitergia our main focus is analyzing software projects using
> > > metrics
> > > > > > > > and we are integrating some of our tools in Allura. We are using
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > a
> > > > > > > > different approach from you, getting the metrics from a
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > consolidated
> > > > > > > > database that gathers the data from Allura, but at the end, the
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > metrics
> > > > > > > > are really similar.
> > > > > > > >
> > > > > > > > We are working in different kind of visualization also, so we
> > > can share
> > > > > > > > also here experiences.
> > > > > > > >
> > > > > > > > > Moreover, it is also possible to see these values for a single
> > > > > > > category
> > > > > > > > > only, namely considering all the data regarding projects
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > tagged as
> > > > > > > > > belonging to that category. A graph showing the number of
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > joined
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > projects
> > > > > > > > > by the user for each category is also shown, to highlight the
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > kind of
> > > > > > > > > applications the user is focused on.
> > > > > > > > > Finally, the previously listed statistics are also calculated
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > for
> > > > > > > > > organizations, by considering the activity of the users
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > enrolled in
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > the
> > > > > > > > > organization itself. Particularly, since each user can
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > possibly work
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > for
> > > > > > > > > more than one organization on the forge, as well as working as
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > an
> > > > > > > > > individual programmer, organizations' statistics are calculated
> > > > > > > >
> > > > > > > >
> > > > > > > > considering
> > > > > > > > > only those activities performed by its members on projects to
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > which
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > the
> > > > > > > > > organizatione is explicitely involved.
> > > > > > > > > We think these features are useful to allow users to have a
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > deeper
> > > > > > > > > awareness of someone else's experience and interests, and this
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > could
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > also
> > > > > > > > > help in identifying partners for a certain project.
> > > > > > > > >
> > > > > > > > > These features are implemented as external features and can be
> > > easily
> > > > > > > > > enabled or disabled by setting boolean parameters in the .ini
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > file.
> > > > > > > > > Therefore, it is possible to enable organizations only, without
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > including
> > > > > > > > > the statistics features, or including statistics for users
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > only, and
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > so
> > > > > > > > on.
> > > > > > > > > Of course, it is not possible to enable organization statistics
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > without
> > > > > > > > > enabling the concept of organization on the forge.
> > > > > > > > >
> > > > > > > > > We would like to know what you think about these features, and
> > > we
> > > > > > > would
> > > > > > > > > like to know how we can provide you our code to get a feedback
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > from
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > you
> > > > > > > > > and, eventually, to discuss improvements and changes on it.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > I think it is a really good use case por the code contributors
> > > policy
> > > > > > > > proposed in the mailing list.
> > > > > > > >
> > > > > > > > > Stefano is now
> > > > > > > > > allowed to write on the repositoy, but since I am not allowed
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > to do
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > so,
> > > > > > > > and
> > > > > > > > > since these features should obviously be discussed before being
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > included
> > > > > > > > on
> > > > > > > > > the project, I don't know if working there, even on a new
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > branch, is
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > the
> > > > > > > > > best solution.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > I think so. Create a new experimental branch and upload the code
> > > to
> > > > > > > > Allura so for others developers like me, it is easy to start
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > playing
> > > > > > > > with it.
> > > > > > > >
> > > > > > > > Cheers
> > > > > > > >
> > > > > > > > > Also, let us know if you prefer to check the two features
> > > > > > > > > separately or not. Probably, it would be easier to do it
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > incrementally,
> > > > > > > > > considering one of them at a time.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > >
> > > > > > > > > Simone Gatti and Stefano Invernizzi
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > |\_____/| Alvaro del Castillo
> > > > > > > > [o] [o] acs@bitergia.com (mailto:acs@bitergia.com) (mailto:acs@bitergia.com) - CTO,
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > Software Engineer
> > > > > > > > | V | http://www.bitergia.com
> > > > > > > > | |
> > > > > > > > -ooo-ooo-
> > > > > > > > |\_____/| Alvaro del Castillo
> > > > > > > > [o] [o] acs@bitergia.com (mailto:acs@bitergia.com) (mailto:acs@bitergia.com) - CTO,
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > Software Engineer
> > > > > > > > | V | http://www.bitergia.com
> > > > > > > > | |
> > > > > > > > -ooo-ooo-
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> >
> >
> >
> >
>
>
Re: User stats and organizations
Posted by Dave Brondsema <da...@brondsema.net>.
On 3/1/13 12:36 PM, Tim Van Steenburgh wrote:
> I think there are 3 options:
>
> 1. Leave as-is, and write a script to install the tool on existing user projects.
> 2. Make the stats tool installable, but only for user projects.
This isn't an option now, but we do have a ticket for it, it'd be nice to have
https://sourceforge.net/p/allura/tickets/2286/
> 3. Install the stats tool on demand when necessary.
This should be doable by putting it in the "Anchored tools" feature. It's a per
neighborhood setting, so it could be added just for the user-neighborhood:
/u/_admin/overview Then it'll get installed on demand when a user-project is
visited.
>
> I think 1 and 3 are the best choices, and I'm leaning towards 1 b/c it'll keep the code cleaner. Let's wait and see if any one else chimes in with an opinion, and if not, we'll just go with that. In the meantime, I'll just continue testing with a new user instead of an existing one.
>
> Thanks!
>
> Tim
>
>
> On Friday, March 1, 2013 at 12:19 PM, Stefano Invernizzi wrote:
>
>> Yes, that's a good point. At the moment, the tool is automatically
>> installed when a new user is created, but it can't be manually installed,
>> therefore this is a problem we should solve. By changing the installable
>> flag, the problem is solved, but the tool can be plugged within other
>> projects too. I was wondering if it's possible to make a tool installable
>> within user projects only.
>>
>> Regards,
>> Stefano
>> Il giorno 01/mar/2013 16:24, "Tim Van Steenburgh" <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)>
>> ha scritto:
>>
>>> Hey guys, I don't see a way to get the Statistics tool installed for an
>>> existing user. Am I missing something?
>>>
>>> Tim
>>>
>>>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: User stats and organizations
Posted by Tim Van Steenburgh <tv...@gmail.com>.
I think there are 3 options:
1. Leave as-is, and write a script to install the tool on existing user projects.
2. Make the stats tool installable, but only for user projects.
3. Install the stats tool on demand when necessary.
I think 1 and 3 are the best choices, and I'm leaning towards 1 b/c it'll keep the code cleaner. Let's wait and see if any one else chimes in with an opinion, and if not, we'll just go with that. In the meantime, I'll just continue testing with a new user instead of an existing one.
Thanks!
Tim
On Friday, March 1, 2013 at 12:19 PM, Stefano Invernizzi wrote:
> Yes, that's a good point. At the moment, the tool is automatically
> installed when a new user is created, but it can't be manually installed,
> therefore this is a problem we should solve. By changing the installable
> flag, the problem is solved, but the tool can be plugged within other
> projects too. I was wondering if it's possible to make a tool installable
> within user projects only.
>
> Regards,
> Stefano
> Il giorno 01/mar/2013 16:24, "Tim Van Steenburgh" <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)>
> ha scritto:
>
> > Hey guys, I don't see a way to get the Statistics tool installed for an
> > existing user. Am I missing something?
> >
> > Tim
> >
> >
> > On Thursday, February 28, 2013 at 4:02 PM, Stefano Invernizzi wrote:
> >
> > > Hi,
> > > Thanks for rebasing our branch! I moved user stats within the user
> > >
> >
> > project as
> > > a tool. Let us know if this implementation is ok.
> > > Regards,
> > >
> > > Stefano
> > >
> > >
> > > 2013/2/25 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com) (mailto:
> > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > >
> > > > Cool, I just pushed a rebased copy of si/5453. Will look forward to
> > your
> > > > next updates!
> > > >
> > > > --
> > > > Tim Van Steenburgh
> > > >
> > > >
> > > >
> > > > On Monday, February 25, 2013 at 4:27 PM, Stefano Invernizzi wrote:
> > > >
> > > > > Hi Tim,
> > > > >
> > > > > Yes, we know our branch is out of date. We would be very happy if
> > you can
> > > > > rebase it, there's no problem about that!
> > > > > The idea of moving user stats within the user project is also very
> > > > >
> > > >
> > >
> >
> > good.
> > > > >
> > > >
> > > >
> > > > We
> > > > > will change and upload it according to your proposal as soon as
> > > >
> > > >
> > >
> >
> > possible.
> > > > > Thank you very much!
> > > > >
> > > > > Stefano.
> > > > >
> > > > >
> > > > >
> > > > > 2013/2/25 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com) (mailto:
> > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)) (mailto:
> > > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > > > >
> > > > > > Stefano & Simone,
> > > > > >
> > > > > > Hey guys, I started doing some more testing on user stats today,
> > and I
> > > > > > have a couple questions.
> > > > > >
> > > > > > 1. Do you mind if I force-push a rebased-to-master copy of si/5453
> > to
> > > > > > origin? Your branch is quite out-of-date relative to master, and
> > > > >
> > > >
> > >
> >
> > when I
> > > > > > rebased it there were several merge conflicts and other cleanup
> > > > >
> > > >
> > > >
> > > > necessary
> > > > > > to get the code running. You're welcome to do the rebase yourself
> > > > >
> > > >
> > > >
> > >
> >
> > of
> > > > > > course, but if you're not comfortable with that I'd be happy to do
> > > > >
> > > >
> > >
> >
> > it.
> > > > > >
> > > > > > 2. I noticed that all the user stats links are rooted at
> > /userstats. I
> > > > > > think it would be preferable to have the stats tool installed in
> > > > >
> > > >
> > >
> >
> > the
> > > > > >
> > > > >
> > > >
> > > >
> > > > user
> > > > > > projects instead. So, the url would end up looking something like
> > > > > > "/u/admin1/stats". What do you guys think of that idea?
> > > > > >
> > > > > > Tim Van Steenburgh
> > > > > >
> > > > > >
> > > > > > On Saturday, February 23, 2013 at 9:07 AM, Stefano Invernizzi
> > wrote:
> > > > > >
> > > > > > > Yes, we fixed the issue in our code, it should be ok now. At the
> > > > moment,
> > > > > > > when I try to run all the tests I get some errors from other
> > > > > >
> > > > >
> > > >
> > > >
> > > > packages. I
> > > > > > > tried to fix them, but I don't know how to do that, since they
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > come
> > > > > >
> > > > >
> > > >
> > > >
> > > > from
> > > > > > > modules and packages dealing with repositories, and they are
> > > > > >
> > > > >
> > > >
> > > >
> > > > unrelated to
> > > > > > > our code.
> > > > > > > Thank you very much!
> > > > > > > Stefano
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 2013/2/21 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com) (mailto:
> > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)) (mailto:
> > > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)) (mailto:
> > > > > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > > > > > >
> > > > > > > > Hi Simone and Stefano,
> > > > > > > >
> > > > > > > > I pulled your si/5453 branch today to do some more testing. I
> > > > rebased
> > > > > > it
> > > > > > > > against master and kicked off the tests (`./run_tests` in the
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > project
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > root)
> > > > > > > > and got some failures. If you guys can get those fixed up and
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > pushed
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > back,
> > > > > > > > I'll try to wrap up the testing.
> > > > > > > >
> > > > > > > > Thanks!
> > > > > > > >
> > > > > > > > Tim Van Steenburgh
> > > > > > > >
> > > > > > > >
> > > > > > > > On Monday, February 18, 2013 at 2:26 PM, Simone Gatti wrote:
> > > > > > > >
> > > > > > > > > Dear Cory,
> > > > > > > > > what Dave said is correct, we refer to user stats.
> > > > > > > > > I'm sorry for this ambiguity, that we didn't noticed before
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > your
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > comment.
> > > > > > > > > We welcome your *feedback on user stats*, since we have not
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > yet
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > received
> > > > > > > > > many comments yet.
> > > > > > > > >
> > > > > > > > > Simone
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:dave@brondsema.net) (mailto:
> > dave@brondsema.net (mailto:dave@brondsema.net)) (mailto:
> > > > dave@brondsema.net (mailto:dave@brondsema.net)) (mailto:
> > > > > > dave@brondsema.net (mailto:dave@brondsema.net)
> > > > > > > > )>
> > > > > > > > >
> > > > > > > > > > Cory, I think Stefano is referring to user stats, which his
> > > > feature
> > > > > > > > branch
> > > > > > > > > > starts collecting, not user profile data (gender, location,
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > etc).
> > > > > > > > > >
> > > > > > > > > > But on the topic of user profiel data, we've had a least
> > one
> > > > > > > > SourceForge
> > > > > > > > > > user
> > > > > > > > > > communicate to use that he/she thought the fields were
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > required. I
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > can
> > > > > > > > > > see how
> > > > > > > > > > this might be inferred since they're the first thing you
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > see
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > on the
> > > > > > > > > > /auth/prefs/
> > > > > > > > > > form. We might consider labelling those optional, or
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > putting
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > them
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > on a
> > > > > > > > > > separate
> > > > > > > > > > page from "subscriptions" and other sections on that page.
> > > > > > > > > >
> > > > > > > > > > -Dave
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > > > > > > > Stefano,
> > > > > > > > > > >
> > > > > > > > > > > Could a user simply not fill in the personal info fields
> > they
> > > > > > don't
> > > > > > > > wish
> > > > > > > > > > to
> > > > > > > > > > > share? What is the value of entering that info but then
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > not
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > displaying
> > > > > > > > > >
> > > > > > > > > > it;
> > > > > > > > > > > to encourage users to enter it if only for our
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > edification?
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Thanks,
> > > > > > > > > > >
> > > > > > > > > > > Cory
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > > > > > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com) (mailto:
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com)) (mailto:
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com))
> > (mailto:
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com) (mailto:
> > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com)))
> > > > (mailto:
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com) (mailto:
> > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com)) (mailto:
> > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com
> > >
> >
> > )))>
> > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Dear all,
> > > > > > > > > > > >
> > > > > > > > > > > > I recently pushed some new commits allowing a single
> > user
> > > > to
> > > > > > hide
> > > > > > > > his or
> > > > > > > > > > > > her personal statistics. I and Simone implemented it
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > since
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > some
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > users
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > may
> > > > > > > > > > > > prefer not to show this data. In that case, data is
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > still
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > available for
> > > > > > > > > > > > their personal use. However, if you think we should not
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > allow
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > users to
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > do
> > > > > > > > > > > > this, we can simply put it back as it was.
> > > > > > > > > > > > As usual, we hope to get some feedbacks from you about
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > this, as
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > well as
> > > > > > > > > > > > about the rest of submitted code.
> > > > > > > > > > > > It would be great for us if the code could be reviewed
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > and, if
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > you
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > think it
> > > > > > > > > > > > would be useful, included on the forge before we
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > complete
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > the
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > thesis we
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > are
> > > > > > > > > > > > working on.
> > > > > > > > > > > > Thank you very much!
> > > > > > > > > > > > Stefano
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net) (mailto:
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > dave@brondsema.net (mailto:dave@brondsema.net)
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > )
> > > > > > > > > > http://www.brondsema.net : personal
> > > > > > > > > > http://www.splike.com : programming
> > > > > > > > > > <><
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> >
>
>
>
Re: User stats and organizations
Posted by Stefano Invernizzi <st...@gmail.com>.
Yes, that's a good point. At the moment, the tool is automatically
installed when a new user is created, but it can't be manually installed,
therefore this is a problem we should solve. By changing the installable
flag, the problem is solved, but the tool can be plugged within other
projects too. I was wondering if it's possible to make a tool installable
within user projects only.
Regards,
Stefano
Il giorno 01/mar/2013 16:24, "Tim Van Steenburgh" <tv...@gmail.com>
ha scritto:
> Hey guys, I don't see a way to get the Statistics tool installed for an
> existing user. Am I missing something?
>
> Tim
>
>
> On Thursday, February 28, 2013 at 4:02 PM, Stefano Invernizzi wrote:
>
> > Hi,
> > Thanks for rebasing our branch! I moved user stats within the user
> project as
> > a tool. Let us know if this implementation is ok.
> > Regards,
> >
> > Stefano
> >
> >
> > 2013/2/25 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> tvansteenburgh@gmail.com)>
> >
> > > Cool, I just pushed a rebased copy of si/5453. Will look forward to
> your
> > > next updates!
> > >
> > > --
> > > Tim Van Steenburgh
> > >
> > >
> > >
> > > On Monday, February 25, 2013 at 4:27 PM, Stefano Invernizzi wrote:
> > >
> > > > Hi Tim,
> > > >
> > > > Yes, we know our branch is out of date. We would be very happy if
> you can
> > > > rebase it, there's no problem about that!
> > > > The idea of moving user stats within the user project is also very
> good.
> > > >
> > >
> > > We
> > > > will change and upload it according to your proposal as soon as
> possible.
> > > > Thank you very much!
> > > >
> > > > Stefano.
> > > >
> > > >
> > > >
> > > > 2013/2/25 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> tvansteenburgh@gmail.com) (mailto:
> > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > > >
> > > > > Stefano & Simone,
> > > > >
> > > > > Hey guys, I started doing some more testing on user stats today,
> and I
> > > > > have a couple questions.
> > > > >
> > > > > 1. Do you mind if I force-push a rebased-to-master copy of si/5453
> to
> > > > > origin? Your branch is quite out-of-date relative to master, and
> when I
> > > > > rebased it there were several merge conflicts and other cleanup
> > > > >
> > > >
> > > >
> > >
> > > necessary
> > > > > to get the code running. You're welcome to do the rebase yourself
> of
> > > > > course, but if you're not comfortable with that I'd be happy to do
> it.
> > > > >
> > > > > 2. I noticed that all the user stats links are rooted at
> /userstats. I
> > > > > think it would be preferable to have the stats tool installed in
> the
> > > > >
> > > >
> > >
> > > user
> > > > > projects instead. So, the url would end up looking something like
> > > > > "/u/admin1/stats". What do you guys think of that idea?
> > > > >
> > > > > Tim Van Steenburgh
> > > > >
> > > > >
> > > > > On Saturday, February 23, 2013 at 9:07 AM, Stefano Invernizzi
> wrote:
> > > > >
> > > > > > Yes, we fixed the issue in our code, it should be ok now. At the
> > > moment,
> > > > > > when I try to run all the tests I get some errors from other
> > > > >
> > > >
> > >
> > > packages. I
> > > > > > tried to fix them, but I don't know how to do that, since they
> come
> > > > >
> > > >
> > >
> > > from
> > > > > > modules and packages dealing with repositories, and they are
> > > > >
> > > >
> > >
> > > unrelated to
> > > > > > our code.
> > > > > > Thank you very much!
> > > > > > Stefano
> > > > > >
> > > > > >
> > > > > >
> > > > > > 2013/2/21 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> tvansteenburgh@gmail.com) (mailto:
> > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)) (mailto:
> > > > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > > > > >
> > > > > > > Hi Simone and Stefano,
> > > > > > >
> > > > > > > I pulled your si/5453 branch today to do some more testing. I
> > > rebased
> > > > > it
> > > > > > > against master and kicked off the tests (`./run_tests` in the
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > project
> > > > > >
> > > > >
> > > > >
> > > > > root)
> > > > > > > and got some failures. If you guys can get those fixed up and
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > pushed
> > > > > >
> > > > >
> > > > >
> > > > > back,
> > > > > > > I'll try to wrap up the testing.
> > > > > > >
> > > > > > > Thanks!
> > > > > > >
> > > > > > > Tim Van Steenburgh
> > > > > > >
> > > > > > >
> > > > > > > On Monday, February 18, 2013 at 2:26 PM, Simone Gatti wrote:
> > > > > > >
> > > > > > > > Dear Cory,
> > > > > > > > what Dave said is correct, we refer to user stats.
> > > > > > > > I'm sorry for this ambiguity, that we didn't noticed before
> your
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > comment.
> > > > > > > > We welcome your *feedback on user stats*, since we have not
> yet
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > received
> > > > > > > > many comments yet.
> > > > > > > >
> > > > > > > > Simone
> > > > > > > >
> > > > > > > >
> > > > > > > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:
> dave@brondsema.net) (mailto:
> > > dave@brondsema.net (mailto:dave@brondsema.net)) (mailto:
> > > > > dave@brondsema.net (mailto:dave@brondsema.net)
> > > > > > > )>
> > > > > > > >
> > > > > > > > > Cory, I think Stefano is referring to user stats, which his
> > > feature
> > > > > > > branch
> > > > > > > > > starts collecting, not user profile data (gender, location,
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > etc).
> > > > > > > > >
> > > > > > > > > But on the topic of user profiel data, we've had a least
> one
> > > > > > > SourceForge
> > > > > > > > > user
> > > > > > > > > communicate to use that he/she thought the fields were
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > required. I
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > can
> > > > > > > > > see how
> > > > > > > > > this might be inferred since they're the first thing you
> see
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > on the
> > > > > > > > > /auth/prefs/
> > > > > > > > > form. We might consider labelling those optional, or
> putting
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > them
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > on a
> > > > > > > > > separate
> > > > > > > > > page from "subscriptions" and other sections on that page.
> > > > > > > > >
> > > > > > > > > -Dave
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > > > > > > Stefano,
> > > > > > > > > >
> > > > > > > > > > Could a user simply not fill in the personal info fields
> they
> > > > > don't
> > > > > > > wish
> > > > > > > > > to
> > > > > > > > > > share? What is the value of entering that info but then
> not
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > displaying
> > > > > > > > >
> > > > > > > > > it;
> > > > > > > > > > to encourage users to enter it if only for our
> edification?
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Thanks,
> > > > > > > > > >
> > > > > > > > > > Cory
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > > > > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com) (mailto:
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com))
> (mailto:
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com))
> > > (mailto:
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com) (mailto:
> > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com
> )))>
> > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Dear all,
> > > > > > > > > > >
> > > > > > > > > > > I recently pushed some new commits allowing a single
> user
> > > to
> > > > > hide
> > > > > > > his or
> > > > > > > > > > > her personal statistics. I and Simone implemented it
> since
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > some
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > users
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > may
> > > > > > > > > > > prefer not to show this data. In that case, data is
> still
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > available for
> > > > > > > > > > > their personal use. However, if you think we should not
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > allow
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > users to
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > do
> > > > > > > > > > > this, we can simply put it back as it was.
> > > > > > > > > > > As usual, we hope to get some feedbacks from you about
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > this, as
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > well as
> > > > > > > > > > > about the rest of submitted code.
> > > > > > > > > > > It would be great for us if the code could be reviewed
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > and, if
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > you
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > think it
> > > > > > > > > > > would be useful, included on the forge before we
> complete
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > the
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > thesis we
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > are
> > > > > > > > > > > working on.
> > > > > > > > > > > Thank you very much!
> > > > > > > > > > > Stefano
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Dave Brondsema : dave@brondsema.net (mailto:
> dave@brondsema.net
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > )
> > > > > > > > > http://www.brondsema.net : personal
> > > > > > > > > http://www.splike.com : programming
> > > > > > > > > <><
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> >
> >
> >
>
>
>
Re: User stats and organizations
Posted by Tim Van Steenburgh <tv...@gmail.com>.
Hey guys, I don't see a way to get the Statistics tool installed for an existing user. Am I missing something?
Tim
On Thursday, February 28, 2013 at 4:02 PM, Stefano Invernizzi wrote:
> Hi,
> Thanks for rebasing our branch! I moved user stats within the user project as
> a tool. Let us know if this implementation is ok.
> Regards,
>
> Stefano
>
>
> 2013/2/25 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)>
>
> > Cool, I just pushed a rebased copy of si/5453. Will look forward to your
> > next updates!
> >
> > --
> > Tim Van Steenburgh
> >
> >
> >
> > On Monday, February 25, 2013 at 4:27 PM, Stefano Invernizzi wrote:
> >
> > > Hi Tim,
> > >
> > > Yes, we know our branch is out of date. We would be very happy if you can
> > > rebase it, there's no problem about that!
> > > The idea of moving user stats within the user project is also very good.
> > >
> >
> > We
> > > will change and upload it according to your proposal as soon as possible.
> > > Thank you very much!
> > >
> > > Stefano.
> > >
> > >
> > >
> > > 2013/2/25 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com) (mailto:
> > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > >
> > > > Stefano & Simone,
> > > >
> > > > Hey guys, I started doing some more testing on user stats today, and I
> > > > have a couple questions.
> > > >
> > > > 1. Do you mind if I force-push a rebased-to-master copy of si/5453 to
> > > > origin? Your branch is quite out-of-date relative to master, and when I
> > > > rebased it there were several merge conflicts and other cleanup
> > > >
> > >
> > >
> >
> > necessary
> > > > to get the code running. You're welcome to do the rebase yourself of
> > > > course, but if you're not comfortable with that I'd be happy to do it.
> > > >
> > > > 2. I noticed that all the user stats links are rooted at /userstats. I
> > > > think it would be preferable to have the stats tool installed in the
> > > >
> > >
> >
> > user
> > > > projects instead. So, the url would end up looking something like
> > > > "/u/admin1/stats". What do you guys think of that idea?
> > > >
> > > > Tim Van Steenburgh
> > > >
> > > >
> > > > On Saturday, February 23, 2013 at 9:07 AM, Stefano Invernizzi wrote:
> > > >
> > > > > Yes, we fixed the issue in our code, it should be ok now. At the
> > moment,
> > > > > when I try to run all the tests I get some errors from other
> > > >
> > >
> >
> > packages. I
> > > > > tried to fix them, but I don't know how to do that, since they come
> > > >
> > >
> >
> > from
> > > > > modules and packages dealing with repositories, and they are
> > > >
> > >
> >
> > unrelated to
> > > > > our code.
> > > > > Thank you very much!
> > > > > Stefano
> > > > >
> > > > >
> > > > >
> > > > > 2013/2/21 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com) (mailto:
> > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)) (mailto:
> > > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > > > >
> > > > > > Hi Simone and Stefano,
> > > > > >
> > > > > > I pulled your si/5453 branch today to do some more testing. I
> > rebased
> > > > it
> > > > > > against master and kicked off the tests (`./run_tests` in the
> > > > >
> > > >
> > > >
> > >
> >
> > project
> > > > >
> > > >
> > > >
> > > > root)
> > > > > > and got some failures. If you guys can get those fixed up and
> > > > >
> > > >
> > > >
> > >
> >
> > pushed
> > > > >
> > > >
> > > >
> > > > back,
> > > > > > I'll try to wrap up the testing.
> > > > > >
> > > > > > Thanks!
> > > > > >
> > > > > > Tim Van Steenburgh
> > > > > >
> > > > > >
> > > > > > On Monday, February 18, 2013 at 2:26 PM, Simone Gatti wrote:
> > > > > >
> > > > > > > Dear Cory,
> > > > > > > what Dave said is correct, we refer to user stats.
> > > > > > > I'm sorry for this ambiguity, that we didn't noticed before your
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > comment.
> > > > > > > We welcome your *feedback on user stats*, since we have not yet
> > > > > >
> > > > >
> > > >
> > > >
> > > > received
> > > > > > > many comments yet.
> > > > > > >
> > > > > > > Simone
> > > > > > >
> > > > > > >
> > > > > > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:dave@brondsema.net) (mailto:
> > dave@brondsema.net (mailto:dave@brondsema.net)) (mailto:
> > > > dave@brondsema.net (mailto:dave@brondsema.net)
> > > > > > )>
> > > > > > >
> > > > > > > > Cory, I think Stefano is referring to user stats, which his
> > feature
> > > > > > branch
> > > > > > > > starts collecting, not user profile data (gender, location,
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > etc).
> > > > > > > >
> > > > > > > > But on the topic of user profiel data, we've had a least one
> > > > > > SourceForge
> > > > > > > > user
> > > > > > > > communicate to use that he/she thought the fields were
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > required. I
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > can
> > > > > > > > see how
> > > > > > > > this might be inferred since they're the first thing you see
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > on the
> > > > > > > > /auth/prefs/
> > > > > > > > form. We might consider labelling those optional, or putting
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > them
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > on a
> > > > > > > > separate
> > > > > > > > page from "subscriptions" and other sections on that page.
> > > > > > > >
> > > > > > > > -Dave
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > > > > > Stefano,
> > > > > > > > >
> > > > > > > > > Could a user simply not fill in the personal info fields they
> > > > don't
> > > > > > wish
> > > > > > > > to
> > > > > > > > > share? What is the value of entering that info but then not
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > displaying
> > > > > > > >
> > > > > > > > it;
> > > > > > > > > to encourage users to enter it if only for our edification?
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > >
> > > > > > > > > Cory
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > > > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com) (mailto:
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com)) (mailto:
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com))
> > (mailto:
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com) (mailto:
> > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com)))>
> > > > wrote:
> > > > > > > > >
> > > > > > > > > > Dear all,
> > > > > > > > > >
> > > > > > > > > > I recently pushed some new commits allowing a single user
> > to
> > > > hide
> > > > > > his or
> > > > > > > > > > her personal statistics. I and Simone implemented it since
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > some
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > users
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > may
> > > > > > > > > > prefer not to show this data. In that case, data is still
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > available for
> > > > > > > > > > their personal use. However, if you think we should not
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > allow
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > users to
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > do
> > > > > > > > > > this, we can simply put it back as it was.
> > > > > > > > > > As usual, we hope to get some feedbacks from you about
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > this, as
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > well as
> > > > > > > > > > about the rest of submitted code.
> > > > > > > > > > It would be great for us if the code could be reviewed
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > and, if
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > you
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > think it
> > > > > > > > > > would be useful, included on the forge before we complete
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > the
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > thesis we
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > are
> > > > > > > > > > working on.
> > > > > > > > > > Thank you very much!
> > > > > > > > > > Stefano
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > )
> > > > > > > > http://www.brondsema.net : personal
> > > > > > > > http://www.splike.com : programming
> > > > > > > > <><
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
>
>
>
Re: User stats and organizations
Posted by Stefano Invernizzi <st...@gmail.com>.
Hi,
Thanks for rebasing our branch! I moved user stats within the user project as
a tool. Let us know if this implementation is ok.
Regards,
Stefano
2013/2/25 Tim Van Steenburgh <tv...@gmail.com>
> Cool, I just pushed a rebased copy of si/5453. Will look forward to your
> next updates!
>
> --
> Tim Van Steenburgh
>
>
>
> On Monday, February 25, 2013 at 4:27 PM, Stefano Invernizzi wrote:
>
> > Hi Tim,
> >
> > Yes, we know our branch is out of date. We would be very happy if you can
> > rebase it, there's no problem about that!
> > The idea of moving user stats within the user project is also very good.
> We
> > will change and upload it according to your proposal as soon as possible.
> > Thank you very much!
> >
> > Stefano.
> >
> >
> >
> > 2013/2/25 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> tvansteenburgh@gmail.com)>
> >
> > > Stefano & Simone,
> > >
> > > Hey guys, I started doing some more testing on user stats today, and I
> > > have a couple questions.
> > >
> > > 1. Do you mind if I force-push a rebased-to-master copy of si/5453 to
> > > origin? Your branch is quite out-of-date relative to master, and when I
> > > rebased it there were several merge conflicts and other cleanup
> necessary
> > > to get the code running. You're welcome to do the rebase yourself of
> > > course, but if you're not comfortable with that I'd be happy to do it.
> > >
> > > 2. I noticed that all the user stats links are rooted at /userstats. I
> > > think it would be preferable to have the stats tool installed in the
> user
> > > projects instead. So, the url would end up looking something like
> > > "/u/admin1/stats". What do you guys think of that idea?
> > >
> > > Tim Van Steenburgh
> > >
> > >
> > > On Saturday, February 23, 2013 at 9:07 AM, Stefano Invernizzi wrote:
> > >
> > > > Yes, we fixed the issue in our code, it should be ok now. At the
> moment,
> > > > when I try to run all the tests I get some errors from other
> packages. I
> > > > tried to fix them, but I don't know how to do that, since they come
> from
> > > > modules and packages dealing with repositories, and they are
> unrelated to
> > > > our code.
> > > > Thank you very much!
> > > > Stefano
> > > >
> > > >
> > > >
> > > > 2013/2/21 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> tvansteenburgh@gmail.com) (mailto:
> > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > > >
> > > > > Hi Simone and Stefano,
> > > > >
> > > > > I pulled your si/5453 branch today to do some more testing. I
> rebased
> > > it
> > > > > against master and kicked off the tests (`./run_tests` in the
> project
> > > >
> > >
> > > root)
> > > > > and got some failures. If you guys can get those fixed up and
> pushed
> > > >
> > >
> > > back,
> > > > > I'll try to wrap up the testing.
> > > > >
> > > > > Thanks!
> > > > >
> > > > > Tim Van Steenburgh
> > > > >
> > > > >
> > > > > On Monday, February 18, 2013 at 2:26 PM, Simone Gatti wrote:
> > > > >
> > > > > > Dear Cory,
> > > > > > what Dave said is correct, we refer to user stats.
> > > > > > I'm sorry for this ambiguity, that we didn't noticed before your
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > comment.
> > > > > > We welcome your *feedback on user stats*, since we have not yet
> > > > >
> > > >
> > >
> > > received
> > > > > > many comments yet.
> > > > > >
> > > > > > Simone
> > > > > >
> > > > > >
> > > > > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:
> dave@brondsema.net) (mailto:
> > > dave@brondsema.net (mailto:dave@brondsema.net)
> > > > > )>
> > > > > >
> > > > > > > Cory, I think Stefano is referring to user stats, which his
> feature
> > > > > branch
> > > > > > > starts collecting, not user profile data (gender, location,
> etc).
> > > > > > >
> > > > > > > But on the topic of user profiel data, we've had a least one
> > > > > SourceForge
> > > > > > > user
> > > > > > > communicate to use that he/she thought the fields were
> required. I
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > can
> > > > > > > see how
> > > > > > > this might be inferred since they're the first thing you see
> on the
> > > > > > > /auth/prefs/
> > > > > > > form. We might consider labelling those optional, or putting
> them
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > on a
> > > > > > > separate
> > > > > > > page from "subscriptions" and other sections on that page.
> > > > > > >
> > > > > > > -Dave
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > > > > Stefano,
> > > > > > > >
> > > > > > > > Could a user simply not fill in the personal info fields they
> > > don't
> > > > > wish
> > > > > > > to
> > > > > > > > share? What is the value of entering that info but then not
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > displaying
> > > > > > >
> > > > > > > it;
> > > > > > > > to encourage users to enter it if only for our edification?
> > > > > > > >
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > >
> > > > > > > > Cory
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com) (mailto:
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com))
> (mailto:
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com))>
> > > wrote:
> > > > > > > >
> > > > > > > > > Dear all,
> > > > > > > > >
> > > > > > > > > I recently pushed some new commits allowing a single user
> to
> > > hide
> > > > > his or
> > > > > > > > > her personal statistics. I and Simone implemented it since
> some
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > users
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > may
> > > > > > > > > prefer not to show this data. In that case, data is still
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > available for
> > > > > > > > > their personal use. However, if you think we should not
> allow
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > users to
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > do
> > > > > > > > > this, we can simply put it back as it was.
> > > > > > > > > As usual, we hope to get some feedbacks from you about
> this, as
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > well as
> > > > > > > > > about the rest of submitted code.
> > > > > > > > > It would be great for us if the code could be reviewed
> and, if
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > you
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > think it
> > > > > > > > > would be useful, included on the forge before we complete
> the
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > thesis we
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > are
> > > > > > > > > working on.
> > > > > > > > > Thank you very much!
> > > > > > > > > Stefano
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net
> )
> > > > > > > http://www.brondsema.net : personal
> > > > > > > http://www.splike.com : programming
> > > > > > > <><
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> >
> >
> >
>
>
>
Re: User stats and organizations
Posted by Tim Van Steenburgh <tv...@gmail.com>.
Cool, I just pushed a rebased copy of si/5453. Will look forward to your next updates!
--
Tim Van Steenburgh
On Monday, February 25, 2013 at 4:27 PM, Stefano Invernizzi wrote:
> Hi Tim,
>
> Yes, we know our branch is out of date. We would be very happy if you can
> rebase it, there's no problem about that!
> The idea of moving user stats within the user project is also very good. We
> will change and upload it according to your proposal as soon as possible.
> Thank you very much!
>
> Stefano.
>
>
>
> 2013/2/25 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)>
>
> > Stefano & Simone,
> >
> > Hey guys, I started doing some more testing on user stats today, and I
> > have a couple questions.
> >
> > 1. Do you mind if I force-push a rebased-to-master copy of si/5453 to
> > origin? Your branch is quite out-of-date relative to master, and when I
> > rebased it there were several merge conflicts and other cleanup necessary
> > to get the code running. You're welcome to do the rebase yourself of
> > course, but if you're not comfortable with that I'd be happy to do it.
> >
> > 2. I noticed that all the user stats links are rooted at /userstats. I
> > think it would be preferable to have the stats tool installed in the user
> > projects instead. So, the url would end up looking something like
> > "/u/admin1/stats". What do you guys think of that idea?
> >
> > Tim Van Steenburgh
> >
> >
> > On Saturday, February 23, 2013 at 9:07 AM, Stefano Invernizzi wrote:
> >
> > > Yes, we fixed the issue in our code, it should be ok now. At the moment,
> > > when I try to run all the tests I get some errors from other packages. I
> > > tried to fix them, but I don't know how to do that, since they come from
> > > modules and packages dealing with repositories, and they are unrelated to
> > > our code.
> > > Thank you very much!
> > > Stefano
> > >
> > >
> > >
> > > 2013/2/21 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com) (mailto:
> > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > >
> > > > Hi Simone and Stefano,
> > > >
> > > > I pulled your si/5453 branch today to do some more testing. I rebased
> > it
> > > > against master and kicked off the tests (`./run_tests` in the project
> > >
> >
> > root)
> > > > and got some failures. If you guys can get those fixed up and pushed
> > >
> >
> > back,
> > > > I'll try to wrap up the testing.
> > > >
> > > > Thanks!
> > > >
> > > > Tim Van Steenburgh
> > > >
> > > >
> > > > On Monday, February 18, 2013 at 2:26 PM, Simone Gatti wrote:
> > > >
> > > > > Dear Cory,
> > > > > what Dave said is correct, we refer to user stats.
> > > > > I'm sorry for this ambiguity, that we didn't noticed before your
> > > > >
> > > >
> > > >
> > >
> >
> > comment.
> > > > > We welcome your *feedback on user stats*, since we have not yet
> > > >
> > >
> >
> > received
> > > > > many comments yet.
> > > > >
> > > > > Simone
> > > > >
> > > > >
> > > > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:dave@brondsema.net) (mailto:
> > dave@brondsema.net (mailto:dave@brondsema.net)
> > > > )>
> > > > >
> > > > > > Cory, I think Stefano is referring to user stats, which his feature
> > > > branch
> > > > > > starts collecting, not user profile data (gender, location, etc).
> > > > > >
> > > > > > But on the topic of user profiel data, we've had a least one
> > > > SourceForge
> > > > > > user
> > > > > > communicate to use that he/she thought the fields were required. I
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > can
> > > > > > see how
> > > > > > this might be inferred since they're the first thing you see on the
> > > > > > /auth/prefs/
> > > > > > form. We might consider labelling those optional, or putting them
> > > > > >
> > > > >
> > > >
> > >
> >
> > on a
> > > > > > separate
> > > > > > page from "subscriptions" and other sections on that page.
> > > > > >
> > > > > > -Dave
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > > > Stefano,
> > > > > > >
> > > > > > > Could a user simply not fill in the personal info fields they
> > don't
> > > > wish
> > > > > > to
> > > > > > > share? What is the value of entering that info but then not
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > displaying
> > > > > >
> > > > > > it;
> > > > > > > to encourage users to enter it if only for our edification?
> > > > > > >
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > Cory
> > > > > > >
> > > > > > >
> > > > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com) (mailto:
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com)) (mailto:
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com))>
> > wrote:
> > > > > > >
> > > > > > > > Dear all,
> > > > > > > >
> > > > > > > > I recently pushed some new commits allowing a single user to
> > hide
> > > > his or
> > > > > > > > her personal statistics. I and Simone implemented it since some
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > users
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > may
> > > > > > > > prefer not to show this data. In that case, data is still
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > available for
> > > > > > > > their personal use. However, if you think we should not allow
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > users to
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > do
> > > > > > > > this, we can simply put it back as it was.
> > > > > > > > As usual, we hope to get some feedbacks from you about this, as
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > well as
> > > > > > > > about the rest of submitted code.
> > > > > > > > It would be great for us if the code could be reviewed and, if
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > you
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > think it
> > > > > > > > would be useful, included on the forge before we complete the
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > thesis we
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > are
> > > > > > > > working on.
> > > > > > > > Thank you very much!
> > > > > > > > Stefano
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net)
> > > > > > http://www.brondsema.net : personal
> > > > > > http://www.splike.com : programming
> > > > > > <><
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> >
>
>
>
Re: User stats and organizations
Posted by Stefano Invernizzi <st...@gmail.com>.
Hi Tim,
Yes, we know our branch is out of date. We would be very happy if you can
rebase it, there's no problem about that!
The idea of moving user stats within the user project is also very good. We
will change and upload it according to your proposal as soon as possible.
Thank you very much!
Stefano.
2013/2/25 Tim Van Steenburgh <tv...@gmail.com>
> Stefano & Simone,
>
> Hey guys, I started doing some more testing on user stats today, and I
> have a couple questions.
>
> 1. Do you mind if I force-push a rebased-to-master copy of si/5453 to
> origin? Your branch is quite out-of-date relative to master, and when I
> rebased it there were several merge conflicts and other cleanup necessary
> to get the code running. You're welcome to do the rebase yourself of
> course, but if you're not comfortable with that I'd be happy to do it.
>
> 2. I noticed that all the user stats links are rooted at /userstats. I
> think it would be preferable to have the stats tool installed in the user
> projects instead. So, the url would end up looking something like
> "/u/admin1/stats". What do you guys think of that idea?
>
> Tim Van Steenburgh
>
>
> On Saturday, February 23, 2013 at 9:07 AM, Stefano Invernizzi wrote:
>
> > Yes, we fixed the issue in our code, it should be ok now. At the moment,
> > when I try to run all the tests I get some errors from other packages. I
> > tried to fix them, but I don't know how to do that, since they come from
> > modules and packages dealing with repositories, and they are unrelated to
> > our code.
> > Thank you very much!
> > Stefano
> >
> >
> >
> > 2013/2/21 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> tvansteenburgh@gmail.com)>
> >
> > > Hi Simone and Stefano,
> > >
> > > I pulled your si/5453 branch today to do some more testing. I rebased
> it
> > > against master and kicked off the tests (`./run_tests` in the project
> root)
> > > and got some failures. If you guys can get those fixed up and pushed
> back,
> > > I'll try to wrap up the testing.
> > >
> > > Thanks!
> > >
> > > Tim Van Steenburgh
> > >
> > >
> > > On Monday, February 18, 2013 at 2:26 PM, Simone Gatti wrote:
> > >
> > > > Dear Cory,
> > > > what Dave said is correct, we refer to user stats.
> > > > I'm sorry for this ambiguity, that we didn't noticed before your
> comment.
> > > > We welcome your *feedback on user stats*, since we have not yet
> received
> > > > many comments yet.
> > > >
> > > > Simone
> > > >
> > > >
> > > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:
> dave@brondsema.net
> > > )>
> > > >
> > > > > Cory, I think Stefano is referring to user stats, which his feature
> > > branch
> > > > > starts collecting, not user profile data (gender, location, etc).
> > > > >
> > > > > But on the topic of user profiel data, we've had a least one
> > > SourceForge
> > > > > user
> > > > > communicate to use that he/she thought the fields were required. I
> can
> > > > > see how
> > > > > this might be inferred since they're the first thing you see on the
> > > > > /auth/prefs/
> > > > > form. We might consider labelling those optional, or putting them
> on a
> > > > > separate
> > > > > page from "subscriptions" and other sections on that page.
> > > > >
> > > > > -Dave
> > > > >
> > > > >
> > > > >
> > > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > > Stefano,
> > > > > >
> > > > > > Could a user simply not fill in the personal info fields they
> don't
> > > wish
> > > > > to
> > > > > > share? What is the value of entering that info but then not
> > > > >
> > > > >
> > > >
> > >
> > > displaying
> > > > >
> > > > > it;
> > > > > > to encourage users to enter it if only for our edification?
> > > > > >
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Cory
> > > > > >
> > > > > >
> > > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com) (mailto:
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com))>
> wrote:
> > > > > >
> > > > > > > Dear all,
> > > > > > >
> > > > > > > I recently pushed some new commits allowing a single user to
> hide
> > > his or
> > > > > > > her personal statistics. I and Simone implemented it since some
> > > > > >
> > > > >
> > > >
> > >
> > > users
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > may
> > > > > > > prefer not to show this data. In that case, data is still
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > available for
> > > > > > > their personal use. However, if you think we should not allow
> > > > > >
> > > > >
> > > >
> > >
> > > users to
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > do
> > > > > > > this, we can simply put it back as it was.
> > > > > > > As usual, we hope to get some feedbacks from you about this, as
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > well as
> > > > > > > about the rest of submitted code.
> > > > > > > It would be great for us if the code could be reviewed and, if
> you
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > think it
> > > > > > > would be useful, included on the forge before we complete the
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > thesis we
> > > > > >
> > > > >
> > > > >
> > > > > are
> > > > > > > working on.
> > > > > > > Thank you very much!
> > > > > > > Stefano
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net)
> > > > > http://www.brondsema.net : personal
> > > > > http://www.splike.com : programming
> > > > > <><
> > > > >
> > > >
> > >
> > >
> >
> >
> >
>
>
>
Re: User stats and organizations
Posted by Tim Van Steenburgh <tv...@gmail.com>.
Stefano & Simone,
Hey guys, I started doing some more testing on user stats today, and I have a couple questions.
1. Do you mind if I force-push a rebased-to-master copy of si/5453 to origin? Your branch is quite out-of-date relative to master, and when I rebased it there were several merge conflicts and other cleanup necessary to get the code running. You're welcome to do the rebase yourself of course, but if you're not comfortable with that I'd be happy to do it.
2. I noticed that all the user stats links are rooted at /userstats. I think it would be preferable to have the stats tool installed in the user projects instead. So, the url would end up looking something like "/u/admin1/stats". What do you guys think of that idea?
Tim Van Steenburgh
On Saturday, February 23, 2013 at 9:07 AM, Stefano Invernizzi wrote:
> Yes, we fixed the issue in our code, it should be ok now. At the moment,
> when I try to run all the tests I get some errors from other packages. I
> tried to fix them, but I don't know how to do that, since they come from
> modules and packages dealing with repositories, and they are unrelated to
> our code.
> Thank you very much!
> Stefano
>
>
>
> 2013/2/21 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)>
>
> > Hi Simone and Stefano,
> >
> > I pulled your si/5453 branch today to do some more testing. I rebased it
> > against master and kicked off the tests (`./run_tests` in the project root)
> > and got some failures. If you guys can get those fixed up and pushed back,
> > I'll try to wrap up the testing.
> >
> > Thanks!
> >
> > Tim Van Steenburgh
> >
> >
> > On Monday, February 18, 2013 at 2:26 PM, Simone Gatti wrote:
> >
> > > Dear Cory,
> > > what Dave said is correct, we refer to user stats.
> > > I'm sorry for this ambiguity, that we didn't noticed before your comment.
> > > We welcome your *feedback on user stats*, since we have not yet received
> > > many comments yet.
> > >
> > > Simone
> > >
> > >
> > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:dave@brondsema.net
> > )>
> > >
> > > > Cory, I think Stefano is referring to user stats, which his feature
> > branch
> > > > starts collecting, not user profile data (gender, location, etc).
> > > >
> > > > But on the topic of user profiel data, we've had a least one
> > SourceForge
> > > > user
> > > > communicate to use that he/she thought the fields were required. I can
> > > > see how
> > > > this might be inferred since they're the first thing you see on the
> > > > /auth/prefs/
> > > > form. We might consider labelling those optional, or putting them on a
> > > > separate
> > > > page from "subscriptions" and other sections on that page.
> > > >
> > > > -Dave
> > > >
> > > >
> > > >
> > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > Stefano,
> > > > >
> > > > > Could a user simply not fill in the personal info fields they don't
> > wish
> > > > to
> > > > > share? What is the value of entering that info but then not
> > > >
> > > >
> > >
> >
> > displaying
> > > >
> > > > it;
> > > > > to encourage users to enter it if only for our edification?
> > > > >
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Cory
> > > > >
> > > > >
> > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com) (mailto:
> > > > >
> > > >
> > > >
> > >
> >
> > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com))> wrote:
> > > > >
> > > > > > Dear all,
> > > > > >
> > > > > > I recently pushed some new commits allowing a single user to hide
> > his or
> > > > > > her personal statistics. I and Simone implemented it since some
> > > > >
> > > >
> > >
> >
> > users
> > > > > >
> > > > >
> > > >
> > > >
> > > > may
> > > > > > prefer not to show this data. In that case, data is still
> > > > >
> > > >
> > > >
> > >
> >
> > available for
> > > > > > their personal use. However, if you think we should not allow
> > > > >
> > > >
> > >
> >
> > users to
> > > > > >
> > > > >
> > > >
> > > >
> > > > do
> > > > > > this, we can simply put it back as it was.
> > > > > > As usual, we hope to get some feedbacks from you about this, as
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > well as
> > > > > > about the rest of submitted code.
> > > > > > It would be great for us if the code could be reviewed and, if you
> > > > > >
> > > > >
> > > >
> > > >
> > > > think it
> > > > > > would be useful, included on the forge before we complete the
> > > > >
> > > >
> > > >
> > >
> >
> > thesis we
> > > > >
> > > >
> > > >
> > > > are
> > > > > > working on.
> > > > > > Thank you very much!
> > > > > > Stefano
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net)
> > > > http://www.brondsema.net : personal
> > > > http://www.splike.com : programming
> > > > <><
> > > >
> > >
> >
> >
>
>
>
Re: User stats and organizations
Posted by Simone Gatti <si...@gmail.com>.
Dear all,
few weeks ago I have created a ticket to propose, together with Stefano,
the inclusion of the concept of organization within the forge. You can find
the ticket with a detailed description of our proposal
here<https://sourceforge.net/p/allura/tickets/5566/>
.
Recently, I created a patch including the code which implements this
concept, and Stefano has pushed it within a new branch on the repository,
named sg/5566.
If you want, you can try it and let us know what you think about our code,
proposing improvements if necessary.
Simone
2013/2/23 Stefano Invernizzi <st...@gmail.com>
> Yes, we fixed the issue in our code, it should be ok now. At the moment,
> when I try to run all the tests I get some errors from other packages. I
> tried to fix them, but I don't know how to do that, since they come from
> modules and packages dealing with repositories, and they are unrelated to
> our code.
> Thank you very much!
> Stefano
>
>
>
> 2013/2/21 Tim Van Steenburgh <tv...@gmail.com>
>
> > Hi Simone and Stefano,
> >
> > I pulled your si/5453 branch today to do some more testing. I rebased it
> > against master and kicked off the tests (`./run_tests` in the project
> root)
> > and got some failures. If you guys can get those fixed up and pushed
> back,
> > I'll try to wrap up the testing.
> >
> > Thanks!
> >
> > Tim Van Steenburgh
> >
> >
> > On Monday, February 18, 2013 at 2:26 PM, Simone Gatti wrote:
> >
> > > Dear Cory,
> > > what Dave said is correct, we refer to user stats.
> > > I'm sorry for this ambiguity, that we didn't noticed before your
> comment.
> > > We welcome your *feedback on user stats*, since we have not yet
> received
> > > many comments yet.
> > >
> > > Simone
> > >
> > >
> > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:
> dave@brondsema.net
> > )>
> > >
> > > > Cory, I think Stefano is referring to user stats, which his feature
> > branch
> > > > starts collecting, not user profile data (gender, location, etc).
> > > >
> > > > But on the topic of user profiel data, we've had a least one
> > SourceForge
> > > > user
> > > > communicate to use that he/she thought the fields were required. I
> can
> > > > see how
> > > > this might be inferred since they're the first thing you see on the
> > > > /auth/prefs/
> > > > form. We might consider labelling those optional, or putting them on
> a
> > > > separate
> > > > page from "subscriptions" and other sections on that page.
> > > >
> > > > -Dave
> > > >
> > > >
> > > >
> > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > Stefano,
> > > > >
> > > > > Could a user simply not fill in the personal info fields they don't
> > wish
> > > > to
> > > > > share? What is the value of entering that info but then not
> > displaying
> > > >
> > > > it;
> > > > > to encourage users to enter it if only for our edification?
> > > > >
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Cory
> > > > >
> > > > >
> > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > stefano.invernizzi88@gmail.com (mailto:
> > stefano.invernizzi88@gmail.com)> wrote:
> > > > >
> > > > > > Dear all,
> > > > > >
> > > > > > I recently pushed some new commits allowing a single user to hide
> > his or
> > > > > > her personal statistics. I and Simone implemented it since some
> > users
> > > > > >
> > > > >
> > > > >
> > > >
> > > > may
> > > > > > prefer not to show this data. In that case, data is still
> > available for
> > > > > > their personal use. However, if you think we should not allow
> > users to
> > > > > >
> > > > >
> > > >
> > > > do
> > > > > > this, we can simply put it back as it was.
> > > > > > As usual, we hope to get some feedbacks from you about this, as
> > well as
> > > > > > about the rest of submitted code.
> > > > > > It would be great for us if the code could be reviewed and, if
> you
> > > > > >
> > > > >
> > > >
> > > > think it
> > > > > > would be useful, included on the forge before we complete the
> > thesis we
> > > > >
> > > >
> > > > are
> > > > > > working on.
> > > > > > Thank you very much!
> > > > > > Stefano
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net)
> > > > http://www.brondsema.net : personal
> > > > http://www.splike.com : programming
> > > > <><
> > > >
> > >
> > >
> > >
> >
> >
> >
>
Re: User stats and organizations
Posted by Stefano Invernizzi <st...@gmail.com>.
Yes, we fixed the issue in our code, it should be ok now. At the moment,
when I try to run all the tests I get some errors from other packages. I
tried to fix them, but I don't know how to do that, since they come from
modules and packages dealing with repositories, and they are unrelated to
our code.
Thank you very much!
Stefano
2013/2/21 Tim Van Steenburgh <tv...@gmail.com>
> Hi Simone and Stefano,
>
> I pulled your si/5453 branch today to do some more testing. I rebased it
> against master and kicked off the tests (`./run_tests` in the project root)
> and got some failures. If you guys can get those fixed up and pushed back,
> I'll try to wrap up the testing.
>
> Thanks!
>
> Tim Van Steenburgh
>
>
> On Monday, February 18, 2013 at 2:26 PM, Simone Gatti wrote:
>
> > Dear Cory,
> > what Dave said is correct, we refer to user stats.
> > I'm sorry for this ambiguity, that we didn't noticed before your comment.
> > We welcome your *feedback on user stats*, since we have not yet received
> > many comments yet.
> >
> > Simone
> >
> >
> > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:dave@brondsema.net
> )>
> >
> > > Cory, I think Stefano is referring to user stats, which his feature
> branch
> > > starts collecting, not user profile data (gender, location, etc).
> > >
> > > But on the topic of user profiel data, we've had a least one
> SourceForge
> > > user
> > > communicate to use that he/she thought the fields were required. I can
> > > see how
> > > this might be inferred since they're the first thing you see on the
> > > /auth/prefs/
> > > form. We might consider labelling those optional, or putting them on a
> > > separate
> > > page from "subscriptions" and other sections on that page.
> > >
> > > -Dave
> > >
> > >
> > >
> > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > Stefano,
> > > >
> > > > Could a user simply not fill in the personal info fields they don't
> wish
> > > to
> > > > share? What is the value of entering that info but then not
> displaying
> > >
> > > it;
> > > > to encourage users to enter it if only for our edification?
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Cory
> > > >
> > > >
> > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com)> wrote:
> > > >
> > > > > Dear all,
> > > > >
> > > > > I recently pushed some new commits allowing a single user to hide
> his or
> > > > > her personal statistics. I and Simone implemented it since some
> users
> > > > >
> > > >
> > > >
> > >
> > > may
> > > > > prefer not to show this data. In that case, data is still
> available for
> > > > > their personal use. However, if you think we should not allow
> users to
> > > > >
> > > >
> > >
> > > do
> > > > > this, we can simply put it back as it was.
> > > > > As usual, we hope to get some feedbacks from you about this, as
> well as
> > > > > about the rest of submitted code.
> > > > > It would be great for us if the code could be reviewed and, if you
> > > > >
> > > >
> > >
> > > think it
> > > > > would be useful, included on the forge before we complete the
> thesis we
> > > >
> > >
> > > are
> > > > > working on.
> > > > > Thank you very much!
> > > > > Stefano
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > > --
> > > Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net)
> > > http://www.brondsema.net : personal
> > > http://www.splike.com : programming
> > > <><
> > >
> >
> >
> >
>
>
>
Re: User stats and organizations
Posted by Tim Van Steenburgh <tv...@gmail.com>.
Hi Simone and Stefano,
I pulled your si/5453 branch today to do some more testing. I rebased it against master and kicked off the tests (`./run_tests` in the project root) and got some failures. If you guys can get those fixed up and pushed back, I'll try to wrap up the testing.
Thanks!
Tim Van Steenburgh
On Monday, February 18, 2013 at 2:26 PM, Simone Gatti wrote:
> Dear Cory,
> what Dave said is correct, we refer to user stats.
> I'm sorry for this ambiguity, that we didn't noticed before your comment.
> We welcome your *feedback on user stats*, since we have not yet received
> many comments yet.
>
> Simone
>
>
> 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:dave@brondsema.net)>
>
> > Cory, I think Stefano is referring to user stats, which his feature branch
> > starts collecting, not user profile data (gender, location, etc).
> >
> > But on the topic of user profiel data, we've had a least one SourceForge
> > user
> > communicate to use that he/she thought the fields were required. I can
> > see how
> > this might be inferred since they're the first thing you see on the
> > /auth/prefs/
> > form. We might consider labelling those optional, or putting them on a
> > separate
> > page from "subscriptions" and other sections on that page.
> >
> > -Dave
> >
> >
> >
> > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > Stefano,
> > >
> > > Could a user simply not fill in the personal info fields they don't wish
> > to
> > > share? What is the value of entering that info but then not displaying
> >
> > it;
> > > to encourage users to enter it if only for our edification?
> > >
> > >
> > > Thanks,
> > >
> > > Cory
> > >
> > >
> > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com)> wrote:
> > >
> > > > Dear all,
> > > >
> > > > I recently pushed some new commits allowing a single user to hide his or
> > > > her personal statistics. I and Simone implemented it since some users
> > > >
> > >
> > >
> >
> > may
> > > > prefer not to show this data. In that case, data is still available for
> > > > their personal use. However, if you think we should not allow users to
> > > >
> > >
> >
> > do
> > > > this, we can simply put it back as it was.
> > > > As usual, we hope to get some feedbacks from you about this, as well as
> > > > about the rest of submitted code.
> > > > It would be great for us if the code could be reviewed and, if you
> > > >
> > >
> >
> > think it
> > > > would be useful, included on the forge before we complete the thesis we
> > >
> >
> > are
> > > > working on.
> > > > Thank you very much!
> > > > Stefano
> > > >
> > >
> >
> >
> >
> >
> > --
> > Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net)
> > http://www.brondsema.net : personal
> > http://www.splike.com : programming
> > <><
> >
>
>
>
Re: User stats and organizations
Posted by Simone Gatti <si...@gmail.com>.
Dear Cory,
what Dave said is correct, we refer to user stats.
I'm sorry for this ambiguity, that we didn't noticed before your comment.
We welcome your *feedback on user stats*, since we have not yet received
many comments yet.
Simone
2013/2/18 Dave Brondsema <da...@brondsema.net>
> Cory, I think Stefano is referring to user stats, which his feature branch
> starts collecting, not user profile data (gender, location, etc).
>
> But on the topic of user profiel data, we've had a least one SourceForge
> user
> communicate to use that he/she thought the fields were required. I can
> see how
> this might be inferred since they're the first thing you see on the
> /auth/prefs/
> form. We might consider labelling those optional, or putting them on a
> separate
> page from "subscriptions" and other sections on that page.
>
> -Dave
>
>
>
> On 2/18/13 9:55 AM, Cory Johns wrote:
> > Stefano,
> >
> > Could a user simply not fill in the personal info fields they don't wish
> to
> > share? What is the value of entering that info but then not displaying
> it;
> > to encourage users to enter it if only for our edification?
> >
> >
> > Thanks,
> >
> > Cory
> >
> >
> > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > stefano.invernizzi88@gmail.com> wrote:
> >
> >> Dear all,
> >>
> >> I recently pushed some new commits allowing a single user to hide his or
> >> her personal statistics. I and Simone implemented it since some users
> may
> >> prefer not to show this data. In that case, data is still available for
> >> their personal use. However, if you think we should not allow users to
> do
> >> this, we can simply put it back as it was.
> >> As usual, we hope to get some feedbacks from you about this, as well as
> >> about the rest of submitted code.
> >> It would be great for us if the code could be reviewed and, if you
> think it
> >> would be useful, included on the forge before we complete the thesis we
> are
> >> working on.
> >> Thank you very much!
> >> Stefano
> >>
>
>
>
> --
> Dave Brondsema : dave@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
Re: User stats and organizations
Posted by Dave Brondsema <da...@brondsema.net>.
On 3/4/13 10:15 AM, Cory Johns wrote:
> Stefano,
>
> +1 on removing the enabled flag now that it's a tool. I agree that it is
> superfluous.
>
+1
> I think what Dave was suggesting is to manually change the Users
> Neighborhood to include userstats and then whenever a user's profile is
> visited, it will cause the userstats to be installed at that time. We
Yep. Having it in bootstrap.py for new Allura instances, and requiring a little
manual work for existing Allura instances is fine I think.
> could also maybe create a ScriptTask to "touch" each user profile to force
> it to be installed if it needs to be present before a user actually visits
> a profile. I may be misunderstanding here, though.
>
>
> On Sun, Mar 3, 2013 at 4:35 AM, Stefano Invernizzi <
> stefano.invernizzi88@gmail.com> wrote:
>
>> Thanks Dave for your suggestion! I modified the bootstrap.py file, so that
>> when the Users neighborhood is created, our tool for userstats is set as an
>> anchored tool, and it perfectly works. However, that way, if you do not run
>> the bootstrap.py, you have to manually add the tool to the anchored ones.
>> And this is what happens in most cases for users who don't want to
>> re-initialize the forge.
>>
>> I was also thinking about the setting in the .ini file to enable userstats.
>> I think it doesn't make sense to disable them now that stats are
>> implemented as a tool. By setting userstats.enable = false, the tool is
>> still installed for users who were using it, therefore I think it's better
>> to remove this option, since it would be confusing. That way, a user who
>> wants to install the forge without using userstats can simply avoid
>> installing the ForgeUserStats tool. I committed this change too, but if you
>> think it's better to think again about it, I'm open to different proposals.
>> Thanks again,
>>
>> Stefano
>>
>>
>>
>> 2013/3/2 Simone Gatti <si...@gmail.com>
>>
>>> Dear Dave,
>>> I have changed the preference page in order to meet these requests.
>>> I created two new pages to collect data about contacts and availability.
>>> In the preference page, over the links, it is now indicated that these
>>> personal data are not compulsory.
>>> In this way, the preference page will no more become so long due to data
>>> about contacts and availability precedently inserted by the user, and the
>>> forms not necessary are not disclosed.
>>> About general personal data, I decided to leave its original form in the
>>> preference page, because it has fixed size and refer to general
>>> information, but I put an explicit indication that they are
>> discretionary.
>>> Please, let me know what do you think about these modifications.
>>> Thanks,
>>> Simone
>>>
>>>
>>> 2013/2/18 Dave Brondsema <da...@brondsema.net>
>>>
>>>> Cory, I think Stefano is referring to user stats, which his feature
>>> branch
>>>> starts collecting, not user profile data (gender, location, etc).
>>>>
>>>> But on the topic of user profiel data, we've had a least one
>> SourceForge
>>>> user
>>>> communicate to use that he/she thought the fields were required. I can
>>>> see how
>>>> this might be inferred since they're the first thing you see on the
>>>> /auth/prefs/
>>>> form. We might consider labelling those optional, or putting them on a
>>>> separate
>>>> page from "subscriptions" and other sections on that page.
>>>>
>>>> -Dave
>>>>
>>>>
>>>>
>>>> On 2/18/13 9:55 AM, Cory Johns wrote:
>>>>> Stefano,
>>>>>
>>>>> Could a user simply not fill in the personal info fields they don't
>>> wish
>>>> to
>>>>> share? What is the value of entering that info but then not
>> displaying
>>>> it;
>>>>> to encourage users to enter it if only for our edification?
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Cory
>>>>>
>>>>>
>>>>> On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
>>>>> stefano.invernizzi88@gmail.com> wrote:
>>>>>
>>>>>> Dear all,
>>>>>>
>>>>>> I recently pushed some new commits allowing a single user to hide
>> his
>>> or
>>>>>> her personal statistics. I and Simone implemented it since some
>> users
>>>> may
>>>>>> prefer not to show this data. In that case, data is still available
>>> for
>>>>>> their personal use. However, if you think we should not allow users
>> to
>>>> do
>>>>>> this, we can simply put it back as it was.
>>>>>> As usual, we hope to get some feedbacks from you about this, as well
>>> as
>>>>>> about the rest of submitted code.
>>>>>> It would be great for us if the code could be reviewed and, if you
>>>> think it
>>>>>> would be useful, included on the forge before we complete the thesis
>>> we
>>>> are
>>>>>> working on.
>>>>>> Thank you very much!
>>>>>> Stefano
>>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Dave Brondsema : dave@brondsema.net
>>>> http://www.brondsema.net : personal
>>>> http://www.splike.com : programming
>>>> <><
>>>>
>>>
>>
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: User stats and organizations
Posted by Cory Johns <jo...@geek.net>.
Stefano,
+1 on removing the enabled flag now that it's a tool. I agree that it is
superfluous.
I think what Dave was suggesting is to manually change the Users
Neighborhood to include userstats and then whenever a user's profile is
visited, it will cause the userstats to be installed at that time. We
could also maybe create a ScriptTask to "touch" each user profile to force
it to be installed if it needs to be present before a user actually visits
a profile. I may be misunderstanding here, though.
On Sun, Mar 3, 2013 at 4:35 AM, Stefano Invernizzi <
stefano.invernizzi88@gmail.com> wrote:
> Thanks Dave for your suggestion! I modified the bootstrap.py file, so that
> when the Users neighborhood is created, our tool for userstats is set as an
> anchored tool, and it perfectly works. However, that way, if you do not run
> the bootstrap.py, you have to manually add the tool to the anchored ones.
> And this is what happens in most cases for users who don't want to
> re-initialize the forge.
>
> I was also thinking about the setting in the .ini file to enable userstats.
> I think it doesn't make sense to disable them now that stats are
> implemented as a tool. By setting userstats.enable = false, the tool is
> still installed for users who were using it, therefore I think it's better
> to remove this option, since it would be confusing. That way, a user who
> wants to install the forge without using userstats can simply avoid
> installing the ForgeUserStats tool. I committed this change too, but if you
> think it's better to think again about it, I'm open to different proposals.
> Thanks again,
>
> Stefano
>
>
>
> 2013/3/2 Simone Gatti <si...@gmail.com>
>
> > Dear Dave,
> > I have changed the preference page in order to meet these requests.
> > I created two new pages to collect data about contacts and availability.
> > In the preference page, over the links, it is now indicated that these
> > personal data are not compulsory.
> > In this way, the preference page will no more become so long due to data
> > about contacts and availability precedently inserted by the user, and the
> > forms not necessary are not disclosed.
> > About general personal data, I decided to leave its original form in the
> > preference page, because it has fixed size and refer to general
> > information, but I put an explicit indication that they are
> discretionary.
> > Please, let me know what do you think about these modifications.
> > Thanks,
> > Simone
> >
> >
> > 2013/2/18 Dave Brondsema <da...@brondsema.net>
> >
> > > Cory, I think Stefano is referring to user stats, which his feature
> > branch
> > > starts collecting, not user profile data (gender, location, etc).
> > >
> > > But on the topic of user profiel data, we've had a least one
> SourceForge
> > > user
> > > communicate to use that he/she thought the fields were required. I can
> > > see how
> > > this might be inferred since they're the first thing you see on the
> > > /auth/prefs/
> > > form. We might consider labelling those optional, or putting them on a
> > > separate
> > > page from "subscriptions" and other sections on that page.
> > >
> > > -Dave
> > >
> > >
> > >
> > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > Stefano,
> > > >
> > > > Could a user simply not fill in the personal info fields they don't
> > wish
> > > to
> > > > share? What is the value of entering that info but then not
> displaying
> > > it;
> > > > to encourage users to enter it if only for our edification?
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Cory
> > > >
> > > >
> > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > stefano.invernizzi88@gmail.com> wrote:
> > > >
> > > >> Dear all,
> > > >>
> > > >> I recently pushed some new commits allowing a single user to hide
> his
> > or
> > > >> her personal statistics. I and Simone implemented it since some
> users
> > > may
> > > >> prefer not to show this data. In that case, data is still available
> > for
> > > >> their personal use. However, if you think we should not allow users
> to
> > > do
> > > >> this, we can simply put it back as it was.
> > > >> As usual, we hope to get some feedbacks from you about this, as well
> > as
> > > >> about the rest of submitted code.
> > > >> It would be great for us if the code could be reviewed and, if you
> > > think it
> > > >> would be useful, included on the forge before we complete the thesis
> > we
> > > are
> > > >> working on.
> > > >> Thank you very much!
> > > >> Stefano
> > > >>
> > >
> > >
> > >
> > > --
> > > Dave Brondsema : dave@brondsema.net
> > > http://www.brondsema.net : personal
> > > http://www.splike.com : programming
> > > <><
> > >
> >
>
--
====
This e- mail message is intended only for the named recipient(s) above. It
may contain confidential and privileged information. If you are not the
intended recipient you are hereby notified that any dissemination,
distribution or copying of this e-mail and any attachment(s) is strictly
prohibited. If you have received this e-mail in error, please immediately
notify the sender by replying to this e-mail and delete the message and any
attachment(s) from your system. Thank you.
Re: User stats and organizations
Posted by Simone Gatti <si...@gmail.com>.
Dear all,
Yesterday we uploaded the code concerning organizations' statistics and we
would be happy to get some feeback from anyone. This commit represents the
last part of the work we developed for our graduation thesis, and it
completes the code which includes organization profiles on the forge. You
can find everything on the branch si/5566.
Please, let us know what you think about it. Thank you!
Regards,
Simone
2013/3/13 Stefano Invernizzi <st...@gmail.com>
> Thank you for fixing the error related to SVN! We did not focus on errors
> from other tests, because we had some problems in running them even in the
> versions of the code which don't include our package. However, we have now
> figured out that we should take more care of it.
> Some of the errors we had were related to the fact we didn't have IPython
> and SQLAlchemy. Should we add them to the requirements-common file? I
> realized we only have them in requirements-sf.
> For what concerns the issues related to the session flush, I thought it was
> safer to have it within the code, but I was probably wrong and, as you
> said, it's probably useless to have an explicit flush. I removed it and
> everything still works, and tests are now successful. I was thinking about
> whether the failure we got was revealing some other issue, but I don't
> think so.
> Anyway, I run all the the tests of all the packages and everything looks
> fine now. Obviously, if there is something wrong in these fixes, let us
> know about it and we'll do our best to improve it.
> Thanks again for helping us to improve our code!
> Stefano
>
>
> 2013/3/12 Tim Van Steenburgh <tv...@gmail.com>
>
> > Hey guys,
> >
> > A couple things:
> >
> > 1. I force-pushed a fix for the failing SVN test.
> > 2. About your latest fix for the session flush failure: I think we may
> > want to dig deeper on this one. The Ming Session represents the
> collection
> > of objects that Ming knows about, be they new, updated, or deleted. When
> a
> > flush happens, Ming iterates through the objects in the Session and
> applies
> > them to the mongo - creating new documents, updating documents, deleting
> > documents. More specific to this code, if session(user) -> None, it means
> > that Ming doesn't know about that user, which is worrisome at best.
> Another
> > thing to note is that Allura uses some Ming middleware to issue a flush
> at
> > the end of each web request, so explicit flushes in user-code are often
> not
> > necessary at all.
> > 3. After fixing the SVN test, I discovered that many ForgeTracker tests
> > are failing now too, possibly related to the issue above. This needs to
> be
> > investigated as well.
> >
> > Please have a look and see what you can do. If you get stuck or need more
> > help, feel free to post back here.
> >
> > Tim
> >
> >
> > On Saturday, March 9, 2013 at 10:35 AM, Stefano Invernizzi wrote:
> >
> > > Great! The error should be fixed now. Thank you very much!
> > > Stefano
> > >
> > >
> > > 2013/3/8 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> > tvansteenburgh@gmail.com)>
> > >
> > > > Okay, that seems to be working now. Things are looking pretty good -
> > > > getting close to merging! I decided to run the tests one more time,
> > and hit
> > > > an error. If you guys can get the tests passing, I think we'll be
> > ready to
> > > > merge.
> > > >
> > > >
> ======================================================================
> > > > ERROR:
> > > >
> >
> allura.tests.unit.test_post_model.TestPostModel.test_that_it_can_be_approved
> > > >
> ----------------------------------------------------------------------
> > > > Traceback (most recent call last):
> > > > File
> > > >
> >
> "/var/local/env-allura/lib/python2.7/site-packages/nose-1.1.2-py2.7.egg/nose/case.py",
> > > > line 197, in runTest
> > > > self.test(*self.arg)
> > > > File
> > > >
> >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/tests/unit/test_post_model.py",
> > > > line 18, in test_that_it_can_be_approved
> > > > self.post.approve()
> > > > File
> > > >
> >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/discuss.py",
> > > > line 575, in approve
> > > > self.commit()
> > > > File
> > > >
> >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/artifact.py",
> > > > line 382, in commit
> > > > self.type_s, self.mod_date, self.project, c.user)
> > > > File
> > > >
> >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/eventslistener.py",
> > > > line 41, in newArtifact
> > > > self.__iterate('newArtifact', art_type, art_datetime, project, user)
> > > > File
> > > >
> >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/eventslistener.py",
> > > > line 38, in __iterate
> > > > getattr(l, event)(*d)
> > > > File
> > > >
> >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/main.py",
> > > > line 28, in newArtifact
> > > > stats = UserStats.create(user)
> > > > File
> > > >
> >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/model/stats.py",
> > > > line 29, in create
> > > > session(user).flush(user)
> > > > AttributeError: 'NoneType' object has no attribute 'flush'
> > > >
> > > >
> > > > Tim
> > > >
> > > >
> > > > On Thursday, March 7, 2013 at 5:49 PM, Stefano Invernizzi wrote:
> > > >
> > > > > I was not able to recreate your problem, but I realized there was
> an
> > > > error
> > > > > in the code I committed yesterday, and this error is probably the
> > reason
> > > > > why you got the reported exception. I changed it and I hope this
> > fixed
> > > > >
> > > >
> > > > the
> > > > > problem. If the issue is still there, let me know about it.
> > > > > Stefano
> > > > >
> > > > >
> > > > > 2013/3/7 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> > tvansteenburgh@gmail.com) (mailto:
> > > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > > > >
> > > > > > Pulled the latest changes, dropped the userstats collection,
> > pushed a
> > > > > > commit to my test repo, refreshed the commiter's stats page, and
> > got
> > > > > >
> > > > >
> > > > >
> > > >
> > > > this:
> > > > > >
> > > > > > File
> > > >
> >
> '/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/controllers/userstats.py',
> > > > > > line 124 in index
> > > > > > ret_dict['discussionpercentage'] = stats.discussionRanking()
> > > > > > File
> > > > > >
> > > > >
> > > >
> > > >
> >
> '/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/contrib_stats.py',
> > > > > > line 143 in discussionRanking
> > > > > > disccontr = self.getDiscussionContribution()
> > > > > > File
> > > > > >
> > > > >
> > > >
> > > >
> >
> '/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/contrib_stats.py',
> > > > > > line 87 in getDiscussionContribution
> > > > > > tot = artifact.created+artifact.modified
> > > > > > TypeError: unsupported operand type(s) for +: 'NoneType' and
> > 'NoneType'
> > > > > >
> > > > > >
> > > > > > Tim
> > > > > >
> > > > > >
> > > > > > On Wednesday, March 6, 2013 at 4:40 PM, Stefano Invernizzi wrote:
> > > > > >
> > > > > > > Yes, there was an error in the initialization of the stats
> > object. I
> > > > hope
> > > > > > > it's ok now.
> > > > > > > Thank you for reporting it!
> > > > > > > Stefano
> > > > > > >
> > > > > > >
> > > > > > > 2013/3/5 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> > tvansteenburgh@gmail.com) (mailto:
> > > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)) (mailto:
> > > > > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > > > > > >
> > > > > > > > Stefano & Simone,
> > > > > > > >
> > > > > > > > Hey guys. Have been doing some more review on Userstats
> today.
> > I
> > > > > > > > force-pushed a couple small changes to origin/si/5453, so
> make
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > sure you
> > > > > > > > pull those.
> > > > > > > >
> > > > > > > > I ran into an error in the stats code after pushing a commit.
> > It
> > > > was a
> > > > > > > > Ming schema validation error:
> > > > > > > >
> > > > > > > > 208 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1]
> File
> > > >
> >
> '/var/local/env-allura/lib/python2.7/site-packages/Ming-0.3.2dev_20121101-py2.7.egg/ming/schema.py',
> > > > > > > > line 327 in _validate
> > > > > > > > 209 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1]
> raise
> > > > > > > > Invalid(msg, d, None, error_dict=error_dict)
> > > > > > > > 210 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1]
> > Invalid:
> > > > > > > > general:[0]:messages:Not a list or tuple
> > > > > > > > 211 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1]
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > tickets:notdict:
> > > > > > > > []
> > > > > > > >
> > > > > > > >
> > > > > > > > Here's the mongo doc:
> > > > > > > >
> > > > > > > > {
> > > > > > > > "_id" : ObjectId("5136502261b3b44a93a7b36f"),
> > > > > > > > "lastmonth" : {
> > > > > > > > "assignedtickets" : [ ],
> > > > > > > > "commits" : [
> > > > > > > > {
> > > > > > > > "programming_languages" : [ ],
> > > > > > > > "lines" : 1,
> > > > > > > > "categories" : [ ],
> > > > > > > > "datetime" :
> > > > > > > > ISODate("2013-03-05T22:28:22.341Z")
> > > > > > > > }
> > > > > > > > ],
> > > > > > > > "solvedtickets" : [ ],
> > > > > > > > "messages" : [ ],
> > > > > > > > "revokedtickets" : [ ]
> > > > > > > > },
> > > > > > > > "user_id" : ObjectId("510ad21c61b3b426260e7586"),
> > > > > > > > "lastmonthlogins" : [ ],
> > > > > > > > "tot_logins_count" : 0,
> > > > > > > > "registration_date" : ISODate("2013-03-05T20:05:54.676Z"),
> > > > > > > > "general" : [
> > > > > > > > {
> > > > > > > > "tickets" : [ ],
> > > > > > > > "commits" : [
> > > > > > > > {
> > > > > > > > "lines" : 1,
> > > > > > > > "number" : 1,
> > > > > > > > "language" : null
> > > > > > > > }
> > > > > > > > ],
> > > > > > > > "category" : null,
> > > > > > > > "messages" : {
> > > > > > > > "assigned" : 0,
> > > > > > > > "solved" : 0,
> > > > > > > > "totsolvingtime" : 0,
> > > > > > > > "revoked" : 0
> > > > > > > > }
> > > > > > > > }
> > > > > > > > ],
> > > > > > > > "visible" : false,
> > > > > > > > "last_login" : null
> > > > > > > > }
> > > > > > > >
> > > > > > > >
> > > > > > > > As you can see, `general.tickets` is a list, not a dict, but
> > it's
> > > > > > defined
> > > > > > > > as a dict in the schema. Maybe you guys could track that
> down?
> > > > > > > >
> > > > > > > > Tim
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sunday, March 3, 2013 at 4:35 AM, Stefano Invernizzi
> wrote:
> > > > > > > >
> > > > > > > > > Thanks Dave for your suggestion! I modified the
> bootstrap.py
> > > > file, so
> > > > > > > > that
> > > > > > > > > when the Users neighborhood is created, our tool for
> > userstats is
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > set as
> > > > > > > >
> > > > > > > > an
> > > > > > > > > anchored tool, and it perfectly works. However, that way,
> if
> > you
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > do
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > not
> > > > > > > >
> > > > > > > > run
> > > > > > > > > the bootstrap.py, you have to manually add the tool to the
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > anchored
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > ones.
> > > > > > > > > And this is what happens in most cases for users who don't
> > want
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > to
> > > > > > > > > re-initialize the forge.
> > > > > > > > >
> > > > > > > > > I was also thinking about the setting in the .ini file to
> > enable
> > > > > > > > userstats.
> > > > > > > > > I think it doesn't make sense to disable them now that
> stats
> > are
> > > > > > > > > implemented as a tool. By setting userstats.enable = false,
> > the
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > tool
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > is
> > > > > > > > > still installed for users who were using it, therefore I
> > think
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > it's
> > > > > > > >
> > > > > > > >
> > > > > > > > better
> > > > > > > > > to remove this option, since it would be confusing. That
> > way, a
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > user
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > who
> > > > > > > > > wants to install the forge without using userstats can
> simply
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > avoid
> > > > > > > > > installing the ForgeUserStats tool. I committed this change
> > too,
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > but
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > if
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > you
> > > > > > > > > think it's better to think again about it, I'm open to
> > different
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > proposals.
> > > > > > > > > Thanks again,
> > > > > > > > >
> > > > > > > > > Stefano
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > 2013/3/2 Simone Gatti <simone.gatti88@gmail.com (mailto:
> > simone.gatti88@gmail.com) (mailto:
> > > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com)) (mailto:
> > > > > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com))
> > (mailto:
> > > > > > > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com))>
> > > > > > > > >
> > > > > > > > > > Dear Dave,
> > > > > > > > > > I have changed the preference page in order to meet these
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > requests.
> > > > > > > > > > I created two new pages to collect data about contacts
> and
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > availability.
> > > > > > > > > > In the preference page, over the links, it is now
> indicated
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > that
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > these
> > > > > > > > > > personal data are not compulsory.
> > > > > > > > > > In this way, the preference page will no more become so
> > long
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > due to
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > data
> > > > > > > > > > about contacts and availability precedently inserted by
> the
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > user,
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > and
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > the
> > > > > > > > > > forms not necessary are not disclosed.
> > > > > > > > > > About general personal data, I decided to leave its
> > original
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > form
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > in
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > the
> > > > > > > > > > preference page, because it has fixed size and refer to
> > general
> > > > > > > > > > information, but I put an explicit indication that they
> are
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > discretionary.
> > > > > > > > > > Please, let me know what do you think about these
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > modifications.
> > > > > > > > > > Thanks,
> > > > > > > > > > Simone
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:
> > dave@brondsema.net) (mailto:
> > > > dave@brondsema.net (mailto:dave@brondsema.net)) (mailto:
> > > > > > dave@brondsema.net (mailto:dave@brondsema.net)) (mailto:
> > > > > > > > dave@brondsema.net (mailto:dave@brondsema.net))>
> > > > > > > > > >
> > > > > > > > > > > Cory, I think Stefano is referring to user stats, which
> > his
> > > > > > feature
> > > > > > > > > > branch
> > > > > > > > > > > starts collecting, not user profile data (gender,
> > location,
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > etc).
> > > > > > > > > > >
> > > > > > > > > > > But on the topic of user profiel data, we've had a
> least
> > one
> > > > > > > > SourceForge
> > > > > > > > > > > user
> > > > > > > > > > > communicate to use that he/she thought the fields were
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > required.
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > I
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > can
> > > > > > > > > > > see how
> > > > > > > > > > > this might be inferred since they're the first thing
> you
> > see
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > on
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > the
> > > > > > > > > > > /auth/prefs/
> > > > > > > > > > > form. We might consider labelling those optional, or
> > putting
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > them on
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > a
> > > > > > > > > > > separate
> > > > > > > > > > > page from "subscriptions" and other sections on that
> > page.
> > > > > > > > > > >
> > > > > > > > > > > -Dave
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > > > > > > > > Stefano,
> > > > > > > > > > > >
> > > > > > > > > > > > Could a user simply not fill in the personal info
> > fields
> > > > they
> > > > > > don't
> > > > > > > > > > wish
> > > > > > > > > > > to
> > > > > > > > > > > > share? What is the value of entering that info but
> > then not
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > displaying
> > > > > > > > > > >
> > > > > > > > > > > it;
> > > > > > > > > > > > to encourage users to enter it if only for our
> > edification?
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks,
> > > > > > > > > > > >
> > > > > > > > > > > > Cory
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > > > > > > > > stefano.invernizzi88@gmail.com (mailto:
> > stefano.invernizzi88@gmail.com) (mailto:
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com))
> > (mailto:
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > stefano.invernizzi88@gmail.com (mailto:
> > stefano.invernizzi88@gmail.com))
> > > > (mailto:
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > stefano.invernizzi88@gmail.com (mailto:
> > stefano.invernizzi88@gmail.com) (mailto:
> > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com
> > )))>
> > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Dear all,
> > > > > > > > > > > > >
> > > > > > > > > > > > > I recently pushed some new commits allowing a
> single
> > > > user to
> > > > > > > > hide his
> > > > > > > > > > or
> > > > > > > > > > > > > her personal statistics. I and Simone implemented
> it
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > since
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > some
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > users
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > may
> > > > > > > > > > > > > prefer not to show this data. In that case, data is
> > still
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > available
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > for
> > > > > > > > > > > > > their personal use. However, if you think we should
> > not
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > allow
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > users to
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > do
> > > > > > > > > > > > > this, we can simply put it back as it was.
> > > > > > > > > > > > > As usual, we hope to get some feedbacks from you
> > about
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > this,
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > as
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > well
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > as
> > > > > > > > > > > > > about the rest of submitted code.
> > > > > > > > > > > > > It would be great for us if the code could be
> > reviewed
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > and,
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > if
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > you
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > think it
> > > > > > > > > > > > > would be useful, included on the forge before we
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > complete the
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > thesis
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > we
> > > > > > > > > > > are
> > > > > > > > > > > > > working on.
> > > > > > > > > > > > > Thank you very much!
> > > > > > > > > > > > > Stefano
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Dave Brondsema : dave@brondsema.net (mailto:
> > dave@brondsema.net) (mailto:
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > dave@brondsema.net (mailto:dave@brondsema.net))
> > > > > > > > > > > http://www.brondsema.net : personal
> > > > > > > > > > > http://www.splike.com : programming
> > > > > > > > > > > <><
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>
Re: User stats and organizations
Posted by Stefano Invernizzi <st...@gmail.com>.
Thank you for fixing the error related to SVN! We did not focus on errors
from other tests, because we had some problems in running them even in the
versions of the code which don't include our package. However, we have now
figured out that we should take more care of it.
Some of the errors we had were related to the fact we didn't have IPython
and SQLAlchemy. Should we add them to the requirements-common file? I
realized we only have them in requirements-sf.
For what concerns the issues related to the session flush, I thought it was
safer to have it within the code, but I was probably wrong and, as you
said, it's probably useless to have an explicit flush. I removed it and
everything still works, and tests are now successful. I was thinking about
whether the failure we got was revealing some other issue, but I don't
think so.
Anyway, I run all the the tests of all the packages and everything looks
fine now. Obviously, if there is something wrong in these fixes, let us
know about it and we'll do our best to improve it.
Thanks again for helping us to improve our code!
Stefano
2013/3/12 Tim Van Steenburgh <tv...@gmail.com>
> Hey guys,
>
> A couple things:
>
> 1. I force-pushed a fix for the failing SVN test.
> 2. About your latest fix for the session flush failure: I think we may
> want to dig deeper on this one. The Ming Session represents the collection
> of objects that Ming knows about, be they new, updated, or deleted. When a
> flush happens, Ming iterates through the objects in the Session and applies
> them to the mongo - creating new documents, updating documents, deleting
> documents. More specific to this code, if session(user) -> None, it means
> that Ming doesn't know about that user, which is worrisome at best. Another
> thing to note is that Allura uses some Ming middleware to issue a flush at
> the end of each web request, so explicit flushes in user-code are often not
> necessary at all.
> 3. After fixing the SVN test, I discovered that many ForgeTracker tests
> are failing now too, possibly related to the issue above. This needs to be
> investigated as well.
>
> Please have a look and see what you can do. If you get stuck or need more
> help, feel free to post back here.
>
> Tim
>
>
> On Saturday, March 9, 2013 at 10:35 AM, Stefano Invernizzi wrote:
>
> > Great! The error should be fixed now. Thank you very much!
> > Stefano
> >
> >
> > 2013/3/8 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> tvansteenburgh@gmail.com)>
> >
> > > Okay, that seems to be working now. Things are looking pretty good -
> > > getting close to merging! I decided to run the tests one more time,
> and hit
> > > an error. If you guys can get the tests passing, I think we'll be
> ready to
> > > merge.
> > >
> > > ======================================================================
> > > ERROR:
> > >
> allura.tests.unit.test_post_model.TestPostModel.test_that_it_can_be_approved
> > > ----------------------------------------------------------------------
> > > Traceback (most recent call last):
> > > File
> > >
> "/var/local/env-allura/lib/python2.7/site-packages/nose-1.1.2-py2.7.egg/nose/case.py",
> > > line 197, in runTest
> > > self.test(*self.arg)
> > > File
> > >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/tests/unit/test_post_model.py",
> > > line 18, in test_that_it_can_be_approved
> > > self.post.approve()
> > > File
> > >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/discuss.py",
> > > line 575, in approve
> > > self.commit()
> > > File
> > >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/artifact.py",
> > > line 382, in commit
> > > self.type_s, self.mod_date, self.project, c.user)
> > > File
> > >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/eventslistener.py",
> > > line 41, in newArtifact
> > > self.__iterate('newArtifact', art_type, art_datetime, project, user)
> > > File
> > >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/eventslistener.py",
> > > line 38, in __iterate
> > > getattr(l, event)(*d)
> > > File
> > >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/main.py",
> > > line 28, in newArtifact
> > > stats = UserStats.create(user)
> > > File
> > >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/model/stats.py",
> > > line 29, in create
> > > session(user).flush(user)
> > > AttributeError: 'NoneType' object has no attribute 'flush'
> > >
> > >
> > > Tim
> > >
> > >
> > > On Thursday, March 7, 2013 at 5:49 PM, Stefano Invernizzi wrote:
> > >
> > > > I was not able to recreate your problem, but I realized there was an
> > > error
> > > > in the code I committed yesterday, and this error is probably the
> reason
> > > > why you got the reported exception. I changed it and I hope this
> fixed
> > > >
> > >
> > > the
> > > > problem. If the issue is still there, let me know about it.
> > > > Stefano
> > > >
> > > >
> > > > 2013/3/7 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> tvansteenburgh@gmail.com) (mailto:
> > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > > >
> > > > > Pulled the latest changes, dropped the userstats collection,
> pushed a
> > > > > commit to my test repo, refreshed the commiter's stats page, and
> got
> > > > >
> > > >
> > > >
> > >
> > > this:
> > > > >
> > > > > File
> > >
> '/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/controllers/userstats.py',
> > > > > line 124 in index
> > > > > ret_dict['discussionpercentage'] = stats.discussionRanking()
> > > > > File
> > > > >
> > > >
> > >
> > >
> '/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/contrib_stats.py',
> > > > > line 143 in discussionRanking
> > > > > disccontr = self.getDiscussionContribution()
> > > > > File
> > > > >
> > > >
> > >
> > >
> '/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/contrib_stats.py',
> > > > > line 87 in getDiscussionContribution
> > > > > tot = artifact.created+artifact.modified
> > > > > TypeError: unsupported operand type(s) for +: 'NoneType' and
> 'NoneType'
> > > > >
> > > > >
> > > > > Tim
> > > > >
> > > > >
> > > > > On Wednesday, March 6, 2013 at 4:40 PM, Stefano Invernizzi wrote:
> > > > >
> > > > > > Yes, there was an error in the initialization of the stats
> object. I
> > > hope
> > > > > > it's ok now.
> > > > > > Thank you for reporting it!
> > > > > > Stefano
> > > > > >
> > > > > >
> > > > > > 2013/3/5 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> tvansteenburgh@gmail.com) (mailto:
> > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)) (mailto:
> > > > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > > > > >
> > > > > > > Stefano & Simone,
> > > > > > >
> > > > > > > Hey guys. Have been doing some more review on Userstats today.
> I
> > > > > > > force-pushed a couple small changes to origin/si/5453, so make
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > sure you
> > > > > > > pull those.
> > > > > > >
> > > > > > > I ran into an error in the stats code after pushing a commit.
> It
> > > was a
> > > > > > > Ming schema validation error:
> > > > > > >
> > > > > > > 208 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] File
> > >
> '/var/local/env-allura/lib/python2.7/site-packages/Ming-0.3.2dev_20121101-py2.7.egg/ming/schema.py',
> > > > > > > line 327 in _validate
> > > > > > > 209 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] raise
> > > > > > > Invalid(msg, d, None, error_dict=error_dict)
> > > > > > > 210 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1]
> Invalid:
> > > > > > > general:[0]:messages:Not a list or tuple
> > > > > > > 211 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1]
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > tickets:notdict:
> > > > > > > []
> > > > > > >
> > > > > > >
> > > > > > > Here's the mongo doc:
> > > > > > >
> > > > > > > {
> > > > > > > "_id" : ObjectId("5136502261b3b44a93a7b36f"),
> > > > > > > "lastmonth" : {
> > > > > > > "assignedtickets" : [ ],
> > > > > > > "commits" : [
> > > > > > > {
> > > > > > > "programming_languages" : [ ],
> > > > > > > "lines" : 1,
> > > > > > > "categories" : [ ],
> > > > > > > "datetime" :
> > > > > > > ISODate("2013-03-05T22:28:22.341Z")
> > > > > > > }
> > > > > > > ],
> > > > > > > "solvedtickets" : [ ],
> > > > > > > "messages" : [ ],
> > > > > > > "revokedtickets" : [ ]
> > > > > > > },
> > > > > > > "user_id" : ObjectId("510ad21c61b3b426260e7586"),
> > > > > > > "lastmonthlogins" : [ ],
> > > > > > > "tot_logins_count" : 0,
> > > > > > > "registration_date" : ISODate("2013-03-05T20:05:54.676Z"),
> > > > > > > "general" : [
> > > > > > > {
> > > > > > > "tickets" : [ ],
> > > > > > > "commits" : [
> > > > > > > {
> > > > > > > "lines" : 1,
> > > > > > > "number" : 1,
> > > > > > > "language" : null
> > > > > > > }
> > > > > > > ],
> > > > > > > "category" : null,
> > > > > > > "messages" : {
> > > > > > > "assigned" : 0,
> > > > > > > "solved" : 0,
> > > > > > > "totsolvingtime" : 0,
> > > > > > > "revoked" : 0
> > > > > > > }
> > > > > > > }
> > > > > > > ],
> > > > > > > "visible" : false,
> > > > > > > "last_login" : null
> > > > > > > }
> > > > > > >
> > > > > > >
> > > > > > > As you can see, `general.tickets` is a list, not a dict, but
> it's
> > > > > defined
> > > > > > > as a dict in the schema. Maybe you guys could track that down?
> > > > > > >
> > > > > > > Tim
> > > > > > >
> > > > > > >
> > > > > > > On Sunday, March 3, 2013 at 4:35 AM, Stefano Invernizzi wrote:
> > > > > > >
> > > > > > > > Thanks Dave for your suggestion! I modified the bootstrap.py
> > > file, so
> > > > > > > that
> > > > > > > > when the Users neighborhood is created, our tool for
> userstats is
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > set as
> > > > > > >
> > > > > > > an
> > > > > > > > anchored tool, and it perfectly works. However, that way, if
> you
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > do
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > not
> > > > > > >
> > > > > > > run
> > > > > > > > the bootstrap.py, you have to manually add the tool to the
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > anchored
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > ones.
> > > > > > > > And this is what happens in most cases for users who don't
> want
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > to
> > > > > > > > re-initialize the forge.
> > > > > > > >
> > > > > > > > I was also thinking about the setting in the .ini file to
> enable
> > > > > > > userstats.
> > > > > > > > I think it doesn't make sense to disable them now that stats
> are
> > > > > > > > implemented as a tool. By setting userstats.enable = false,
> the
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > tool
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > is
> > > > > > > > still installed for users who were using it, therefore I
> think
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > it's
> > > > > > >
> > > > > > >
> > > > > > > better
> > > > > > > > to remove this option, since it would be confusing. That
> way, a
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > user
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > who
> > > > > > > > wants to install the forge without using userstats can simply
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > avoid
> > > > > > > > installing the ForgeUserStats tool. I committed this change
> too,
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > but
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > if
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > you
> > > > > > > > think it's better to think again about it, I'm open to
> different
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > proposals.
> > > > > > > > Thanks again,
> > > > > > > >
> > > > > > > > Stefano
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > 2013/3/2 Simone Gatti <simone.gatti88@gmail.com (mailto:
> simone.gatti88@gmail.com) (mailto:
> > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com)) (mailto:
> > > > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com))
> (mailto:
> > > > > > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com))>
> > > > > > > >
> > > > > > > > > Dear Dave,
> > > > > > > > > I have changed the preference page in order to meet these
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > requests.
> > > > > > > > > I created two new pages to collect data about contacts and
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > availability.
> > > > > > > > > In the preference page, over the links, it is now indicated
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > that
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > these
> > > > > > > > > personal data are not compulsory.
> > > > > > > > > In this way, the preference page will no more become so
> long
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > due to
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > data
> > > > > > > > > about contacts and availability precedently inserted by the
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > user,
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > and
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > the
> > > > > > > > > forms not necessary are not disclosed.
> > > > > > > > > About general personal data, I decided to leave its
> original
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > form
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > in
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > the
> > > > > > > > > preference page, because it has fixed size and refer to
> general
> > > > > > > > > information, but I put an explicit indication that they are
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > discretionary.
> > > > > > > > > Please, let me know what do you think about these
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > modifications.
> > > > > > > > > Thanks,
> > > > > > > > > Simone
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:
> dave@brondsema.net) (mailto:
> > > dave@brondsema.net (mailto:dave@brondsema.net)) (mailto:
> > > > > dave@brondsema.net (mailto:dave@brondsema.net)) (mailto:
> > > > > > > dave@brondsema.net (mailto:dave@brondsema.net))>
> > > > > > > > >
> > > > > > > > > > Cory, I think Stefano is referring to user stats, which
> his
> > > > > feature
> > > > > > > > > branch
> > > > > > > > > > starts collecting, not user profile data (gender,
> location,
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > etc).
> > > > > > > > > >
> > > > > > > > > > But on the topic of user profiel data, we've had a least
> one
> > > > > > > SourceForge
> > > > > > > > > > user
> > > > > > > > > > communicate to use that he/she thought the fields were
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > required.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > I
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > can
> > > > > > > > > > see how
> > > > > > > > > > this might be inferred since they're the first thing you
> see
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > on
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > the
> > > > > > > > > > /auth/prefs/
> > > > > > > > > > form. We might consider labelling those optional, or
> putting
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > them on
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > a
> > > > > > > > > > separate
> > > > > > > > > > page from "subscriptions" and other sections on that
> page.
> > > > > > > > > >
> > > > > > > > > > -Dave
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > > > > > > > Stefano,
> > > > > > > > > > >
> > > > > > > > > > > Could a user simply not fill in the personal info
> fields
> > > they
> > > > > don't
> > > > > > > > > wish
> > > > > > > > > > to
> > > > > > > > > > > share? What is the value of entering that info but
> then not
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > displaying
> > > > > > > > > >
> > > > > > > > > > it;
> > > > > > > > > > > to encourage users to enter it if only for our
> edification?
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Thanks,
> > > > > > > > > > >
> > > > > > > > > > > Cory
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > > > > > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com) (mailto:
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com))
> (mailto:
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com))
> > > (mailto:
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com) (mailto:
> > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com
> )))>
> > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Dear all,
> > > > > > > > > > > >
> > > > > > > > > > > > I recently pushed some new commits allowing a single
> > > user to
> > > > > > > hide his
> > > > > > > > > or
> > > > > > > > > > > > her personal statistics. I and Simone implemented it
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > since
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > some
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > users
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > may
> > > > > > > > > > > > prefer not to show this data. In that case, data is
> still
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > available
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > for
> > > > > > > > > > > > their personal use. However, if you think we should
> not
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > allow
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > users to
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > do
> > > > > > > > > > > > this, we can simply put it back as it was.
> > > > > > > > > > > > As usual, we hope to get some feedbacks from you
> about
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > this,
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > as
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > well
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > as
> > > > > > > > > > > > about the rest of submitted code.
> > > > > > > > > > > > It would be great for us if the code could be
> reviewed
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > and,
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > if
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > you
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > think it
> > > > > > > > > > > > would be useful, included on the forge before we
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > complete the
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > thesis
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > we
> > > > > > > > > > are
> > > > > > > > > > > > working on.
> > > > > > > > > > > > Thank you very much!
> > > > > > > > > > > > Stefano
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Dave Brondsema : dave@brondsema.net (mailto:
> dave@brondsema.net) (mailto:
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > dave@brondsema.net (mailto:dave@brondsema.net))
> > > > > > > > > > http://www.brondsema.net : personal
> > > > > > > > > > http://www.splike.com : programming
> > > > > > > > > > <><
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> >
> >
> >
>
>
>
Re: User stats and organizations
Posted by Tim Van Steenburgh <tv...@gmail.com>.
Hey guys,
A couple things:
1. I force-pushed a fix for the failing SVN test.
2. About your latest fix for the session flush failure: I think we may want to dig deeper on this one. The Ming Session represents the collection of objects that Ming knows about, be they new, updated, or deleted. When a flush happens, Ming iterates through the objects in the Session and applies them to the mongo - creating new documents, updating documents, deleting documents. More specific to this code, if session(user) -> None, it means that Ming doesn't know about that user, which is worrisome at best. Another thing to note is that Allura uses some Ming middleware to issue a flush at the end of each web request, so explicit flushes in user-code are often not necessary at all.
3. After fixing the SVN test, I discovered that many ForgeTracker tests are failing now too, possibly related to the issue above. This needs to be investigated as well.
Please have a look and see what you can do. If you get stuck or need more help, feel free to post back here.
Tim
On Saturday, March 9, 2013 at 10:35 AM, Stefano Invernizzi wrote:
> Great! The error should be fixed now. Thank you very much!
> Stefano
>
>
> 2013/3/8 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)>
>
> > Okay, that seems to be working now. Things are looking pretty good -
> > getting close to merging! I decided to run the tests one more time, and hit
> > an error. If you guys can get the tests passing, I think we'll be ready to
> > merge.
> >
> > ======================================================================
> > ERROR:
> > allura.tests.unit.test_post_model.TestPostModel.test_that_it_can_be_approved
> > ----------------------------------------------------------------------
> > Traceback (most recent call last):
> > File
> > "/var/local/env-allura/lib/python2.7/site-packages/nose-1.1.2-py2.7.egg/nose/case.py",
> > line 197, in runTest
> > self.test(*self.arg)
> > File
> > "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/tests/unit/test_post_model.py",
> > line 18, in test_that_it_can_be_approved
> > self.post.approve()
> > File
> > "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/discuss.py",
> > line 575, in approve
> > self.commit()
> > File
> > "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/artifact.py",
> > line 382, in commit
> > self.type_s, self.mod_date, self.project, c.user)
> > File
> > "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/eventslistener.py",
> > line 41, in newArtifact
> > self.__iterate('newArtifact', art_type, art_datetime, project, user)
> > File
> > "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/eventslistener.py",
> > line 38, in __iterate
> > getattr(l, event)(*d)
> > File
> > "/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/main.py",
> > line 28, in newArtifact
> > stats = UserStats.create(user)
> > File
> > "/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/model/stats.py",
> > line 29, in create
> > session(user).flush(user)
> > AttributeError: 'NoneType' object has no attribute 'flush'
> >
> >
> > Tim
> >
> >
> > On Thursday, March 7, 2013 at 5:49 PM, Stefano Invernizzi wrote:
> >
> > > I was not able to recreate your problem, but I realized there was an
> > error
> > > in the code I committed yesterday, and this error is probably the reason
> > > why you got the reported exception. I changed it and I hope this fixed
> > >
> >
> > the
> > > problem. If the issue is still there, let me know about it.
> > > Stefano
> > >
> > >
> > > 2013/3/7 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com) (mailto:
> > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > >
> > > > Pulled the latest changes, dropped the userstats collection, pushed a
> > > > commit to my test repo, refreshed the commiter's stats page, and got
> > > >
> > >
> > >
> >
> > this:
> > > >
> > > > File
> > '/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/controllers/userstats.py',
> > > > line 124 in index
> > > > ret_dict['discussionpercentage'] = stats.discussionRanking()
> > > > File
> > > >
> > >
> >
> > '/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/contrib_stats.py',
> > > > line 143 in discussionRanking
> > > > disccontr = self.getDiscussionContribution()
> > > > File
> > > >
> > >
> >
> > '/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/contrib_stats.py',
> > > > line 87 in getDiscussionContribution
> > > > tot = artifact.created+artifact.modified
> > > > TypeError: unsupported operand type(s) for +: 'NoneType' and 'NoneType'
> > > >
> > > >
> > > > Tim
> > > >
> > > >
> > > > On Wednesday, March 6, 2013 at 4:40 PM, Stefano Invernizzi wrote:
> > > >
> > > > > Yes, there was an error in the initialization of the stats object. I
> > hope
> > > > > it's ok now.
> > > > > Thank you for reporting it!
> > > > > Stefano
> > > > >
> > > > >
> > > > > 2013/3/5 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com) (mailto:
> > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)) (mailto:
> > > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > > > >
> > > > > > Stefano & Simone,
> > > > > >
> > > > > > Hey guys. Have been doing some more review on Userstats today. I
> > > > > > force-pushed a couple small changes to origin/si/5453, so make
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > sure you
> > > > > > pull those.
> > > > > >
> > > > > > I ran into an error in the stats code after pushing a commit. It
> > was a
> > > > > > Ming schema validation error:
> > > > > >
> > > > > > 208 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] File
> > '/var/local/env-allura/lib/python2.7/site-packages/Ming-0.3.2dev_20121101-py2.7.egg/ming/schema.py',
> > > > > > line 327 in _validate
> > > > > > 209 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] raise
> > > > > > Invalid(msg, d, None, error_dict=error_dict)
> > > > > > 210 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] Invalid:
> > > > > > general:[0]:messages:Not a list or tuple
> > > > > > 211 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1]
> > > > > >
> > > > >
> > > >
> > > >
> > > > tickets:notdict:
> > > > > > []
> > > > > >
> > > > > >
> > > > > > Here's the mongo doc:
> > > > > >
> > > > > > {
> > > > > > "_id" : ObjectId("5136502261b3b44a93a7b36f"),
> > > > > > "lastmonth" : {
> > > > > > "assignedtickets" : [ ],
> > > > > > "commits" : [
> > > > > > {
> > > > > > "programming_languages" : [ ],
> > > > > > "lines" : 1,
> > > > > > "categories" : [ ],
> > > > > > "datetime" :
> > > > > > ISODate("2013-03-05T22:28:22.341Z")
> > > > > > }
> > > > > > ],
> > > > > > "solvedtickets" : [ ],
> > > > > > "messages" : [ ],
> > > > > > "revokedtickets" : [ ]
> > > > > > },
> > > > > > "user_id" : ObjectId("510ad21c61b3b426260e7586"),
> > > > > > "lastmonthlogins" : [ ],
> > > > > > "tot_logins_count" : 0,
> > > > > > "registration_date" : ISODate("2013-03-05T20:05:54.676Z"),
> > > > > > "general" : [
> > > > > > {
> > > > > > "tickets" : [ ],
> > > > > > "commits" : [
> > > > > > {
> > > > > > "lines" : 1,
> > > > > > "number" : 1,
> > > > > > "language" : null
> > > > > > }
> > > > > > ],
> > > > > > "category" : null,
> > > > > > "messages" : {
> > > > > > "assigned" : 0,
> > > > > > "solved" : 0,
> > > > > > "totsolvingtime" : 0,
> > > > > > "revoked" : 0
> > > > > > }
> > > > > > }
> > > > > > ],
> > > > > > "visible" : false,
> > > > > > "last_login" : null
> > > > > > }
> > > > > >
> > > > > >
> > > > > > As you can see, `general.tickets` is a list, not a dict, but it's
> > > > defined
> > > > > > as a dict in the schema. Maybe you guys could track that down?
> > > > > >
> > > > > > Tim
> > > > > >
> > > > > >
> > > > > > On Sunday, March 3, 2013 at 4:35 AM, Stefano Invernizzi wrote:
> > > > > >
> > > > > > > Thanks Dave for your suggestion! I modified the bootstrap.py
> > file, so
> > > > > > that
> > > > > > > when the Users neighborhood is created, our tool for userstats is
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > set as
> > > > > >
> > > > > > an
> > > > > > > anchored tool, and it perfectly works. However, that way, if you
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > do
> > > > > >
> > > > >
> > > >
> > > >
> > > > not
> > > > > >
> > > > > > run
> > > > > > > the bootstrap.py, you have to manually add the tool to the
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > anchored
> > > > > >
> > > > >
> > > >
> > > >
> > > > ones.
> > > > > > > And this is what happens in most cases for users who don't want
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > to
> > > > > > > re-initialize the forge.
> > > > > > >
> > > > > > > I was also thinking about the setting in the .ini file to enable
> > > > > > userstats.
> > > > > > > I think it doesn't make sense to disable them now that stats are
> > > > > > > implemented as a tool. By setting userstats.enable = false, the
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > tool
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > is
> > > > > > > still installed for users who were using it, therefore I think
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > it's
> > > > > >
> > > > > >
> > > > > > better
> > > > > > > to remove this option, since it would be confusing. That way, a
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > user
> > > > > >
> > > > >
> > > >
> > > >
> > > > who
> > > > > > > wants to install the forge without using userstats can simply
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > avoid
> > > > > > > installing the ForgeUserStats tool. I committed this change too,
> > > > > >
> > > > >
> > > >
> > >
> >
> > but
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > if
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > you
> > > > > > > think it's better to think again about it, I'm open to different
> > > > > >
> > > > > >
> > > > > >
> > > > > > proposals.
> > > > > > > Thanks again,
> > > > > > >
> > > > > > > Stefano
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 2013/3/2 Simone Gatti <simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com) (mailto:
> > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com)) (mailto:
> > > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com)) (mailto:
> > > > > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com))>
> > > > > > >
> > > > > > > > Dear Dave,
> > > > > > > > I have changed the preference page in order to meet these
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > requests.
> > > > > > > > I created two new pages to collect data about contacts and
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > availability.
> > > > > > > > In the preference page, over the links, it is now indicated
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > that
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > these
> > > > > > > > personal data are not compulsory.
> > > > > > > > In this way, the preference page will no more become so long
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > due to
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > data
> > > > > > > > about contacts and availability precedently inserted by the
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > user,
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > and
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > the
> > > > > > > > forms not necessary are not disclosed.
> > > > > > > > About general personal data, I decided to leave its original
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > form
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > in
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > the
> > > > > > > > preference page, because it has fixed size and refer to general
> > > > > > > > information, but I put an explicit indication that they are
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > discretionary.
> > > > > > > > Please, let me know what do you think about these
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > modifications.
> > > > > > > > Thanks,
> > > > > > > > Simone
> > > > > > > >
> > > > > > > >
> > > > > > > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:dave@brondsema.net) (mailto:
> > dave@brondsema.net (mailto:dave@brondsema.net)) (mailto:
> > > > dave@brondsema.net (mailto:dave@brondsema.net)) (mailto:
> > > > > > dave@brondsema.net (mailto:dave@brondsema.net))>
> > > > > > > >
> > > > > > > > > Cory, I think Stefano is referring to user stats, which his
> > > > feature
> > > > > > > > branch
> > > > > > > > > starts collecting, not user profile data (gender, location,
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > etc).
> > > > > > > > >
> > > > > > > > > But on the topic of user profiel data, we've had a least one
> > > > > > SourceForge
> > > > > > > > > user
> > > > > > > > > communicate to use that he/she thought the fields were
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > required.
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > I
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > can
> > > > > > > > > see how
> > > > > > > > > this might be inferred since they're the first thing you see
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > on
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > the
> > > > > > > > > /auth/prefs/
> > > > > > > > > form. We might consider labelling those optional, or putting
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > them on
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > a
> > > > > > > > > separate
> > > > > > > > > page from "subscriptions" and other sections on that page.
> > > > > > > > >
> > > > > > > > > -Dave
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > > > > > > Stefano,
> > > > > > > > > >
> > > > > > > > > > Could a user simply not fill in the personal info fields
> > they
> > > > don't
> > > > > > > > wish
> > > > > > > > > to
> > > > > > > > > > share? What is the value of entering that info but then not
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > displaying
> > > > > > > > >
> > > > > > > > > it;
> > > > > > > > > > to encourage users to enter it if only for our edification?
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Thanks,
> > > > > > > > > >
> > > > > > > > > > Cory
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > > > > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com) (mailto:
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com)) (mailto:
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com))
> > (mailto:
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com) (mailto:
> > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com)))>
> > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Dear all,
> > > > > > > > > > >
> > > > > > > > > > > I recently pushed some new commits allowing a single
> > user to
> > > > > > hide his
> > > > > > > > or
> > > > > > > > > > > her personal statistics. I and Simone implemented it
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > since
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > some
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > users
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > may
> > > > > > > > > > > prefer not to show this data. In that case, data is still
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > available
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > for
> > > > > > > > > > > their personal use. However, if you think we should not
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > allow
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > users to
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > do
> > > > > > > > > > > this, we can simply put it back as it was.
> > > > > > > > > > > As usual, we hope to get some feedbacks from you about
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > this,
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > as
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > well
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > as
> > > > > > > > > > > about the rest of submitted code.
> > > > > > > > > > > It would be great for us if the code could be reviewed
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > and,
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > if
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > you
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > think it
> > > > > > > > > > > would be useful, included on the forge before we
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > complete the
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > thesis
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > we
> > > > > > > > > are
> > > > > > > > > > > working on.
> > > > > > > > > > > Thank you very much!
> > > > > > > > > > > Stefano
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net) (mailto:
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > dave@brondsema.net (mailto:dave@brondsema.net))
> > > > > > > > > http://www.brondsema.net : personal
> > > > > > > > > http://www.splike.com : programming
> > > > > > > > > <><
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
>
>
>
Re: User stats and organizations
Posted by Simone Gatti <si...@gmail.com>.
Dear all,
due to the recent changes on the package of single user's statistics, that
has become a tool to be installed in the project associated to a user, we
decided to introduce some modifications on the implementation of the
organizations.
In particular, we changed the code so that it now allows the association of
each organization to a project (as it now happens for single users). This
project will contain the organization profile. In this way, organization's
statistics can be easily implemented as a tool to be installed in the
project associated to the organization.
We have already unploaded the code in the branch sg/5566, in order to
collect feedbacks about the modifications produced.
Regards, Simone
2013/3/9 Stefano Invernizzi <st...@gmail.com>
> Great! The error should be fixed now. Thank you very much!
> Stefano
>
>
> 2013/3/8 Tim Van Steenburgh <tv...@gmail.com>
>
> > Okay, that seems to be working now. Things are looking pretty good -
> > getting close to merging! I decided to run the tests one more time, and
> hit
> > an error. If you guys can get the tests passing, I think we'll be ready
> to
> > merge.
> >
> > ======================================================================
> > ERROR:
> >
> allura.tests.unit.test_post_model.TestPostModel.test_that_it_can_be_approved
> > ----------------------------------------------------------------------
> > Traceback (most recent call last):
> > File
> >
> "/var/local/env-allura/lib/python2.7/site-packages/nose-1.1.2-py2.7.egg/nose/case.py",
> > line 197, in runTest
> > self.test(*self.arg)
> > File
> >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/tests/unit/test_post_model.py",
> > line 18, in test_that_it_can_be_approved
> > self.post.approve()
> > File
> >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/discuss.py",
> > line 575, in approve
> > self.commit()
> > File
> >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/artifact.py",
> > line 382, in commit
> > self.type_s, self.mod_date, self.project, c.user)
> > File
> >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/eventslistener.py",
> > line 41, in newArtifact
> > self.__iterate('newArtifact', art_type, art_datetime, project, user)
> > File
> >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/eventslistener.py",
> > line 38, in __iterate
> > getattr(l, event)(*d)
> > File
> >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/main.py",
> > line 28, in newArtifact
> > stats = UserStats.create(user)
> > File
> >
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/model/stats.py",
> > line 29, in create
> > session(user).flush(user)
> > AttributeError: 'NoneType' object has no attribute 'flush'
> >
> >
> > Tim
> >
> >
> > On Thursday, March 7, 2013 at 5:49 PM, Stefano Invernizzi wrote:
> >
> > > I was not able to recreate your problem, but I realized there was an
> > error
> > > in the code I committed yesterday, and this error is probably the
> reason
> > > why you got the reported exception. I changed it and I hope this fixed
> > the
> > > problem. If the issue is still there, let me know about it.
> > > Stefano
> > >
> > >
> > > 2013/3/7 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> > tvansteenburgh@gmail.com)>
> > >
> > > > Pulled the latest changes, dropped the userstats collection, pushed a
> > > > commit to my test repo, refreshed the commiter's stats page, and got
> > this:
> > > >
> > > > File
> > > >
> >
> '/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/controllers/userstats.py',
> > > > line 124 in index
> > > > ret_dict['discussionpercentage'] = stats.discussionRanking()
> > > > File
> > > >
> >
> '/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/contrib_stats.py',
> > > > line 143 in discussionRanking
> > > > disccontr = self.getDiscussionContribution()
> > > > File
> > > >
> >
> '/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/contrib_stats.py',
> > > > line 87 in getDiscussionContribution
> > > > tot = artifact.created+artifact.modified
> > > > TypeError: unsupported operand type(s) for +: 'NoneType' and
> 'NoneType'
> > > >
> > > >
> > > > Tim
> > > >
> > > >
> > > > On Wednesday, March 6, 2013 at 4:40 PM, Stefano Invernizzi wrote:
> > > >
> > > > > Yes, there was an error in the initialization of the stats object.
> I
> > hope
> > > > > it's ok now.
> > > > > Thank you for reporting it!
> > > > > Stefano
> > > > >
> > > > >
> > > > > 2013/3/5 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> > tvansteenburgh@gmail.com) (mailto:
> > > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > > > >
> > > > > > Stefano & Simone,
> > > > > >
> > > > > > Hey guys. Have been doing some more review on Userstats today. I
> > > > > > force-pushed a couple small changes to origin/si/5453, so make
> > sure you
> > > > > > pull those.
> > > > > >
> > > > > > I ran into an error in the stats code after pushing a commit. It
> > was a
> > > > > > Ming schema validation error:
> > > > > >
> > > > > > 208 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] File
> > > >
> >
> '/var/local/env-allura/lib/python2.7/site-packages/Ming-0.3.2dev_20121101-py2.7.egg/ming/schema.py',
> > > > > > line 327 in _validate
> > > > > > 209 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] raise
> > > > > > Invalid(msg, d, None, error_dict=error_dict)
> > > > > > 210 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1]
> Invalid:
> > > > > > general:[0]:messages:Not a list or tuple
> > > > > > 211 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1]
> > > > > >
> > > > >
> > > >
> > > > tickets:notdict:
> > > > > > []
> > > > > >
> > > > > >
> > > > > > Here's the mongo doc:
> > > > > >
> > > > > > {
> > > > > > "_id" : ObjectId("5136502261b3b44a93a7b36f"),
> > > > > > "lastmonth" : {
> > > > > > "assignedtickets" : [ ],
> > > > > > "commits" : [
> > > > > > {
> > > > > > "programming_languages" : [ ],
> > > > > > "lines" : 1,
> > > > > > "categories" : [ ],
> > > > > > "datetime" :
> > > > > > ISODate("2013-03-05T22:28:22.341Z")
> > > > > > }
> > > > > > ],
> > > > > > "solvedtickets" : [ ],
> > > > > > "messages" : [ ],
> > > > > > "revokedtickets" : [ ]
> > > > > > },
> > > > > > "user_id" : ObjectId("510ad21c61b3b426260e7586"),
> > > > > > "lastmonthlogins" : [ ],
> > > > > > "tot_logins_count" : 0,
> > > > > > "registration_date" : ISODate("2013-03-05T20:05:54.676Z"),
> > > > > > "general" : [
> > > > > > {
> > > > > > "tickets" : [ ],
> > > > > > "commits" : [
> > > > > > {
> > > > > > "lines" : 1,
> > > > > > "number" : 1,
> > > > > > "language" : null
> > > > > > }
> > > > > > ],
> > > > > > "category" : null,
> > > > > > "messages" : {
> > > > > > "assigned" : 0,
> > > > > > "solved" : 0,
> > > > > > "totsolvingtime" : 0,
> > > > > > "revoked" : 0
> > > > > > }
> > > > > > }
> > > > > > ],
> > > > > > "visible" : false,
> > > > > > "last_login" : null
> > > > > > }
> > > > > >
> > > > > >
> > > > > > As you can see, `general.tickets` is a list, not a dict, but it's
> > > > defined
> > > > > > as a dict in the schema. Maybe you guys could track that down?
> > > > > >
> > > > > > Tim
> > > > > >
> > > > > >
> > > > > > On Sunday, March 3, 2013 at 4:35 AM, Stefano Invernizzi wrote:
> > > > > >
> > > > > > > Thanks Dave for your suggestion! I modified the bootstrap.py
> > file, so
> > > > > > that
> > > > > > > when the Users neighborhood is created, our tool for userstats
> is
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > set as
> > > > > >
> > > > > > an
> > > > > > > anchored tool, and it perfectly works. However, that way, if
> you
> > do
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > not
> > > > > >
> > > > > > run
> > > > > > > the bootstrap.py, you have to manually add the tool to the
> > anchored
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > ones.
> > > > > > > And this is what happens in most cases for users who don't want
> > to
> > > > > > > re-initialize the forge.
> > > > > > >
> > > > > > > I was also thinking about the setting in the .ini file to
> enable
> > > > > > userstats.
> > > > > > > I think it doesn't make sense to disable them now that stats
> are
> > > > > > > implemented as a tool. By setting userstats.enable = false, the
> > tool
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > is
> > > > > > > still installed for users who were using it, therefore I think
> > it's
> > > > > >
> > > > > >
> > > > > > better
> > > > > > > to remove this option, since it would be confusing. That way, a
> > user
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > who
> > > > > > > wants to install the forge without using userstats can simply
> > avoid
> > > > > > > installing the ForgeUserStats tool. I committed this change
> too,
> > but
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > if
> > > > > > >
> > > > > >
> > > > > >
> > > > > > you
> > > > > > > think it's better to think again about it, I'm open to
> different
> > > > > >
> > > > > >
> > > > > > proposals.
> > > > > > > Thanks again,
> > > > > > >
> > > > > > > Stefano
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > 2013/3/2 Simone Gatti <simone.gatti88@gmail.com (mailto:
> > simone.gatti88@gmail.com) (mailto:
> > > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com)) (mailto:
> > > > > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com))>
> > > > > > >
> > > > > > > > Dear Dave,
> > > > > > > > I have changed the preference page in order to meet these
> > requests.
> > > > > > > > I created two new pages to collect data about contacts and
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > availability.
> > > > > > > > In the preference page, over the links, it is now indicated
> > that
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > these
> > > > > > > > personal data are not compulsory.
> > > > > > > > In this way, the preference page will no more become so long
> > due to
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > data
> > > > > > > > about contacts and availability precedently inserted by the
> > user,
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > and
> > > > > > >
> > > > > >
> > > > > >
> > > > > > the
> > > > > > > > forms not necessary are not disclosed.
> > > > > > > > About general personal data, I decided to leave its original
> > form
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > in
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > the
> > > > > > > > preference page, because it has fixed size and refer to
> general
> > > > > > > > information, but I put an explicit indication that they are
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > discretionary.
> > > > > > > > Please, let me know what do you think about these
> > modifications.
> > > > > > > > Thanks,
> > > > > > > > Simone
> > > > > > > >
> > > > > > > >
> > > > > > > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:
> > dave@brondsema.net) (mailto:
> > > > dave@brondsema.net (mailto:dave@brondsema.net)) (mailto:
> > > > > > dave@brondsema.net (mailto:dave@brondsema.net))>
> > > > > > > >
> > > > > > > > > Cory, I think Stefano is referring to user stats, which his
> > > > feature
> > > > > > > > branch
> > > > > > > > > starts collecting, not user profile data (gender, location,
> > etc).
> > > > > > > > >
> > > > > > > > > But on the topic of user profiel data, we've had a least
> one
> > > > > > SourceForge
> > > > > > > > > user
> > > > > > > > > communicate to use that he/she thought the fields were
> > required.
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > I
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > can
> > > > > > > > > see how
> > > > > > > > > this might be inferred since they're the first thing you
> see
> > on
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > the
> > > > > > > > > /auth/prefs/
> > > > > > > > > form. We might consider labelling those optional, or
> putting
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > them on
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > a
> > > > > > > > > separate
> > > > > > > > > page from "subscriptions" and other sections on that page.
> > > > > > > > >
> > > > > > > > > -Dave
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > > > > > > Stefano,
> > > > > > > > > >
> > > > > > > > > > Could a user simply not fill in the personal info fields
> > they
> > > > don't
> > > > > > > > wish
> > > > > > > > > to
> > > > > > > > > > share? What is the value of entering that info but then
> not
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > displaying
> > > > > > > > >
> > > > > > > > > it;
> > > > > > > > > > to encourage users to enter it if only for our
> edification?
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Thanks,
> > > > > > > > > >
> > > > > > > > > > Cory
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > > > > > > stefano.invernizzi88@gmail.com (mailto:
> > stefano.invernizzi88@gmail.com) (mailto:
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com))
> > (mailto:
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > stefano.invernizzi88@gmail.com (mailto:
> > stefano.invernizzi88@gmail.com))>
> > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Dear all,
> > > > > > > > > > >
> > > > > > > > > > > I recently pushed some new commits allowing a single
> > user to
> > > > > > hide his
> > > > > > > > or
> > > > > > > > > > > her personal statistics. I and Simone implemented it
> > since
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > some
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > users
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > may
> > > > > > > > > > > prefer not to show this data. In that case, data is
> still
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > available
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > for
> > > > > > > > > > > their personal use. However, if you think we should not
> > allow
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > users to
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > do
> > > > > > > > > > > this, we can simply put it back as it was.
> > > > > > > > > > > As usual, we hope to get some feedbacks from you about
> > this,
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > as
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > well
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > as
> > > > > > > > > > > about the rest of submitted code.
> > > > > > > > > > > It would be great for us if the code could be reviewed
> > and,
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > if
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > you
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > think it
> > > > > > > > > > > would be useful, included on the forge before we
> > complete the
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > thesis
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > we
> > > > > > > > > are
> > > > > > > > > > > working on.
> > > > > > > > > > > Thank you very much!
> > > > > > > > > > > Stefano
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Dave Brondsema : dave@brondsema.net (mailto:
> > dave@brondsema.net)
> > > > > > > > > http://www.brondsema.net : personal
> > > > > > > > > http://www.splike.com : programming
> > > > > > > > > <><
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>
Re: User stats and organizations
Posted by Stefano Invernizzi <st...@gmail.com>.
Great! The error should be fixed now. Thank you very much!
Stefano
2013/3/8 Tim Van Steenburgh <tv...@gmail.com>
> Okay, that seems to be working now. Things are looking pretty good -
> getting close to merging! I decided to run the tests one more time, and hit
> an error. If you guys can get the tests passing, I think we'll be ready to
> merge.
>
> ======================================================================
> ERROR:
> allura.tests.unit.test_post_model.TestPostModel.test_that_it_can_be_approved
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File
> "/var/local/env-allura/lib/python2.7/site-packages/nose-1.1.2-py2.7.egg/nose/case.py",
> line 197, in runTest
> self.test(*self.arg)
> File
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/tests/unit/test_post_model.py",
> line 18, in test_that_it_can_be_approved
> self.post.approve()
> File
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/discuss.py",
> line 575, in approve
> self.commit()
> File
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/artifact.py",
> line 382, in commit
> self.type_s, self.mod_date, self.project, c.user)
> File
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/eventslistener.py",
> line 41, in newArtifact
> self.__iterate('newArtifact', art_type, art_datetime, project, user)
> File
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/eventslistener.py",
> line 38, in __iterate
> getattr(l, event)(*d)
> File
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/main.py",
> line 28, in newArtifact
> stats = UserStats.create(user)
> File
> "/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/model/stats.py",
> line 29, in create
> session(user).flush(user)
> AttributeError: 'NoneType' object has no attribute 'flush'
>
>
> Tim
>
>
> On Thursday, March 7, 2013 at 5:49 PM, Stefano Invernizzi wrote:
>
> > I was not able to recreate your problem, but I realized there was an
> error
> > in the code I committed yesterday, and this error is probably the reason
> > why you got the reported exception. I changed it and I hope this fixed
> the
> > problem. If the issue is still there, let me know about it.
> > Stefano
> >
> >
> > 2013/3/7 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> tvansteenburgh@gmail.com)>
> >
> > > Pulled the latest changes, dropped the userstats collection, pushed a
> > > commit to my test repo, refreshed the commiter's stats page, and got
> this:
> > >
> > > File
> > >
> '/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/controllers/userstats.py',
> > > line 124 in index
> > > ret_dict['discussionpercentage'] = stats.discussionRanking()
> > > File
> > >
> '/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/contrib_stats.py',
> > > line 143 in discussionRanking
> > > disccontr = self.getDiscussionContribution()
> > > File
> > >
> '/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/contrib_stats.py',
> > > line 87 in getDiscussionContribution
> > > tot = artifact.created+artifact.modified
> > > TypeError: unsupported operand type(s) for +: 'NoneType' and 'NoneType'
> > >
> > >
> > > Tim
> > >
> > >
> > > On Wednesday, March 6, 2013 at 4:40 PM, Stefano Invernizzi wrote:
> > >
> > > > Yes, there was an error in the initialization of the stats object. I
> hope
> > > > it's ok now.
> > > > Thank you for reporting it!
> > > > Stefano
> > > >
> > > >
> > > > 2013/3/5 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> tvansteenburgh@gmail.com) (mailto:
> > > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > > >
> > > > > Stefano & Simone,
> > > > >
> > > > > Hey guys. Have been doing some more review on Userstats today. I
> > > > > force-pushed a couple small changes to origin/si/5453, so make
> sure you
> > > > > pull those.
> > > > >
> > > > > I ran into an error in the stats code after pushing a commit. It
> was a
> > > > > Ming schema validation error:
> > > > >
> > > > > 208 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] File
> > >
> '/var/local/env-allura/lib/python2.7/site-packages/Ming-0.3.2dev_20121101-py2.7.egg/ming/schema.py',
> > > > > line 327 in _validate
> > > > > 209 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] raise
> > > > > Invalid(msg, d, None, error_dict=error_dict)
> > > > > 210 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] Invalid:
> > > > > general:[0]:messages:Not a list or tuple
> > > > > 211 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1]
> > > > >
> > > >
> > >
> > > tickets:notdict:
> > > > > []
> > > > >
> > > > >
> > > > > Here's the mongo doc:
> > > > >
> > > > > {
> > > > > "_id" : ObjectId("5136502261b3b44a93a7b36f"),
> > > > > "lastmonth" : {
> > > > > "assignedtickets" : [ ],
> > > > > "commits" : [
> > > > > {
> > > > > "programming_languages" : [ ],
> > > > > "lines" : 1,
> > > > > "categories" : [ ],
> > > > > "datetime" :
> > > > > ISODate("2013-03-05T22:28:22.341Z")
> > > > > }
> > > > > ],
> > > > > "solvedtickets" : [ ],
> > > > > "messages" : [ ],
> > > > > "revokedtickets" : [ ]
> > > > > },
> > > > > "user_id" : ObjectId("510ad21c61b3b426260e7586"),
> > > > > "lastmonthlogins" : [ ],
> > > > > "tot_logins_count" : 0,
> > > > > "registration_date" : ISODate("2013-03-05T20:05:54.676Z"),
> > > > > "general" : [
> > > > > {
> > > > > "tickets" : [ ],
> > > > > "commits" : [
> > > > > {
> > > > > "lines" : 1,
> > > > > "number" : 1,
> > > > > "language" : null
> > > > > }
> > > > > ],
> > > > > "category" : null,
> > > > > "messages" : {
> > > > > "assigned" : 0,
> > > > > "solved" : 0,
> > > > > "totsolvingtime" : 0,
> > > > > "revoked" : 0
> > > > > }
> > > > > }
> > > > > ],
> > > > > "visible" : false,
> > > > > "last_login" : null
> > > > > }
> > > > >
> > > > >
> > > > > As you can see, `general.tickets` is a list, not a dict, but it's
> > > defined
> > > > > as a dict in the schema. Maybe you guys could track that down?
> > > > >
> > > > > Tim
> > > > >
> > > > >
> > > > > On Sunday, March 3, 2013 at 4:35 AM, Stefano Invernizzi wrote:
> > > > >
> > > > > > Thanks Dave for your suggestion! I modified the bootstrap.py
> file, so
> > > > > that
> > > > > > when the Users neighborhood is created, our tool for userstats is
> > > > >
> > > > >
> > > >
> > >
> > > set as
> > > > >
> > > > > an
> > > > > > anchored tool, and it perfectly works. However, that way, if you
> do
> > > > >
> > > > >
> > > >
> > >
> > > not
> > > > >
> > > > > run
> > > > > > the bootstrap.py, you have to manually add the tool to the
> anchored
> > > > >
> > > > >
> > > >
> > >
> > > ones.
> > > > > > And this is what happens in most cases for users who don't want
> to
> > > > > > re-initialize the forge.
> > > > > >
> > > > > > I was also thinking about the setting in the .ini file to enable
> > > > > userstats.
> > > > > > I think it doesn't make sense to disable them now that stats are
> > > > > > implemented as a tool. By setting userstats.enable = false, the
> tool
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > is
> > > > > > still installed for users who were using it, therefore I think
> it's
> > > > >
> > > > >
> > > > > better
> > > > > > to remove this option, since it would be confusing. That way, a
> user
> > > > >
> > > > >
> > > >
> > >
> > > who
> > > > > > wants to install the forge without using userstats can simply
> avoid
> > > > > > installing the ForgeUserStats tool. I committed this change too,
> but
> > > > > >
> > > > >
> > > >
> > >
> > > if
> > > > > >
> > > > >
> > > > >
> > > > > you
> > > > > > think it's better to think again about it, I'm open to different
> > > > >
> > > > >
> > > > > proposals.
> > > > > > Thanks again,
> > > > > >
> > > > > > Stefano
> > > > > >
> > > > > >
> > > > > >
> > > > > > 2013/3/2 Simone Gatti <simone.gatti88@gmail.com (mailto:
> simone.gatti88@gmail.com) (mailto:
> > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com)) (mailto:
> > > > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com))>
> > > > > >
> > > > > > > Dear Dave,
> > > > > > > I have changed the preference page in order to meet these
> requests.
> > > > > > > I created two new pages to collect data about contacts and
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > availability.
> > > > > > > In the preference page, over the links, it is now indicated
> that
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > these
> > > > > > > personal data are not compulsory.
> > > > > > > In this way, the preference page will no more become so long
> due to
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > data
> > > > > > > about contacts and availability precedently inserted by the
> user,
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > and
> > > > > >
> > > > >
> > > > >
> > > > > the
> > > > > > > forms not necessary are not disclosed.
> > > > > > > About general personal data, I decided to leave its original
> form
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > in
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > the
> > > > > > > preference page, because it has fixed size and refer to general
> > > > > > > information, but I put an explicit indication that they are
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > discretionary.
> > > > > > > Please, let me know what do you think about these
> modifications.
> > > > > > > Thanks,
> > > > > > > Simone
> > > > > > >
> > > > > > >
> > > > > > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:
> dave@brondsema.net) (mailto:
> > > dave@brondsema.net (mailto:dave@brondsema.net)) (mailto:
> > > > > dave@brondsema.net (mailto:dave@brondsema.net))>
> > > > > > >
> > > > > > > > Cory, I think Stefano is referring to user stats, which his
> > > feature
> > > > > > > branch
> > > > > > > > starts collecting, not user profile data (gender, location,
> etc).
> > > > > > > >
> > > > > > > > But on the topic of user profiel data, we've had a least one
> > > > > SourceForge
> > > > > > > > user
> > > > > > > > communicate to use that he/she thought the fields were
> required.
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > I
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > can
> > > > > > > > see how
> > > > > > > > this might be inferred since they're the first thing you see
> on
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > the
> > > > > > > > /auth/prefs/
> > > > > > > > form. We might consider labelling those optional, or putting
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > them on
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > a
> > > > > > > > separate
> > > > > > > > page from "subscriptions" and other sections on that page.
> > > > > > > >
> > > > > > > > -Dave
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > > > > > Stefano,
> > > > > > > > >
> > > > > > > > > Could a user simply not fill in the personal info fields
> they
> > > don't
> > > > > > > wish
> > > > > > > > to
> > > > > > > > > share? What is the value of entering that info but then not
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > displaying
> > > > > > > >
> > > > > > > > it;
> > > > > > > > > to encourage users to enter it if only for our edification?
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > >
> > > > > > > > > Cory
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > > > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com) (mailto:
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com))
> (mailto:
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com))>
> > > wrote:
> > > > > > > > >
> > > > > > > > > > Dear all,
> > > > > > > > > >
> > > > > > > > > > I recently pushed some new commits allowing a single
> user to
> > > > > hide his
> > > > > > > or
> > > > > > > > > > her personal statistics. I and Simone implemented it
> since
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > some
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > users
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > may
> > > > > > > > > > prefer not to show this data. In that case, data is still
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > available
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > for
> > > > > > > > > > their personal use. However, if you think we should not
> allow
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > users to
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > do
> > > > > > > > > > this, we can simply put it back as it was.
> > > > > > > > > > As usual, we hope to get some feedbacks from you about
> this,
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > as
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > well
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > as
> > > > > > > > > > about the rest of submitted code.
> > > > > > > > > > It would be great for us if the code could be reviewed
> and,
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > if
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > you
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > think it
> > > > > > > > > > would be useful, included on the forge before we
> complete the
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > thesis
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > we
> > > > > > > > are
> > > > > > > > > > working on.
> > > > > > > > > > Thank you very much!
> > > > > > > > > > Stefano
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Dave Brondsema : dave@brondsema.net (mailto:
> dave@brondsema.net)
> > > > > > > > http://www.brondsema.net : personal
> > > > > > > > http://www.splike.com : programming
> > > > > > > > <><
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> >
> >
> >
>
>
>
Re: User stats and organizations
Posted by Tim Van Steenburgh <tv...@gmail.com>.
Okay, that seems to be working now. Things are looking pretty good - getting close to merging! I decided to run the tests one more time, and hit an error. If you guys can get the tests passing, I think we'll be ready to merge.
======================================================================
ERROR: allura.tests.unit.test_post_model.TestPostModel.test_that_it_can_be_approved
----------------------------------------------------------------------
Traceback (most recent call last):
File "/var/local/env-allura/lib/python2.7/site-packages/nose-1.1.2-py2.7.egg/nose/case.py", line 197, in runTest
self.test(*self.arg)
File "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/tests/unit/test_post_model.py", line 18, in test_that_it_can_be_approved
self.post.approve()
File "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/discuss.py", line 575, in approve
self.commit()
File "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/artifact.py", line 382, in commit
self.type_s, self.mod_date, self.project, c.user)
File "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/eventslistener.py", line 41, in newArtifact
self.__iterate('newArtifact', art_type, art_datetime, project, user)
File "/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/eventslistener.py", line 38, in __iterate
getattr(l, event)(*d)
File "/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/main.py", line 28, in newArtifact
stats = UserStats.create(user)
File "/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/model/stats.py", line 29, in create
session(user).flush(user)
AttributeError: 'NoneType' object has no attribute 'flush'
Tim
On Thursday, March 7, 2013 at 5:49 PM, Stefano Invernizzi wrote:
> I was not able to recreate your problem, but I realized there was an error
> in the code I committed yesterday, and this error is probably the reason
> why you got the reported exception. I changed it and I hope this fixed the
> problem. If the issue is still there, let me know about it.
> Stefano
>
>
> 2013/3/7 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)>
>
> > Pulled the latest changes, dropped the userstats collection, pushed a
> > commit to my test repo, refreshed the commiter's stats page, and got this:
> >
> > File
> > '/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/controllers/userstats.py',
> > line 124 in index
> > ret_dict['discussionpercentage'] = stats.discussionRanking()
> > File
> > '/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/contrib_stats.py',
> > line 143 in discussionRanking
> > disccontr = self.getDiscussionContribution()
> > File
> > '/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/contrib_stats.py',
> > line 87 in getDiscussionContribution
> > tot = artifact.created+artifact.modified
> > TypeError: unsupported operand type(s) for +: 'NoneType' and 'NoneType'
> >
> >
> > Tim
> >
> >
> > On Wednesday, March 6, 2013 at 4:40 PM, Stefano Invernizzi wrote:
> >
> > > Yes, there was an error in the initialization of the stats object. I hope
> > > it's ok now.
> > > Thank you for reporting it!
> > > Stefano
> > >
> > >
> > > 2013/3/5 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com) (mailto:
> > tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com))>
> > >
> > > > Stefano & Simone,
> > > >
> > > > Hey guys. Have been doing some more review on Userstats today. I
> > > > force-pushed a couple small changes to origin/si/5453, so make sure you
> > > > pull those.
> > > >
> > > > I ran into an error in the stats code after pushing a commit. It was a
> > > > Ming schema validation error:
> > > >
> > > > 208 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] File
> > '/var/local/env-allura/lib/python2.7/site-packages/Ming-0.3.2dev_20121101-py2.7.egg/ming/schema.py',
> > > > line 327 in _validate
> > > > 209 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] raise
> > > > Invalid(msg, d, None, error_dict=error_dict)
> > > > 210 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] Invalid:
> > > > general:[0]:messages:Not a list or tuple
> > > > 211 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1]
> > > >
> > >
> >
> > tickets:notdict:
> > > > []
> > > >
> > > >
> > > > Here's the mongo doc:
> > > >
> > > > {
> > > > "_id" : ObjectId("5136502261b3b44a93a7b36f"),
> > > > "lastmonth" : {
> > > > "assignedtickets" : [ ],
> > > > "commits" : [
> > > > {
> > > > "programming_languages" : [ ],
> > > > "lines" : 1,
> > > > "categories" : [ ],
> > > > "datetime" :
> > > > ISODate("2013-03-05T22:28:22.341Z")
> > > > }
> > > > ],
> > > > "solvedtickets" : [ ],
> > > > "messages" : [ ],
> > > > "revokedtickets" : [ ]
> > > > },
> > > > "user_id" : ObjectId("510ad21c61b3b426260e7586"),
> > > > "lastmonthlogins" : [ ],
> > > > "tot_logins_count" : 0,
> > > > "registration_date" : ISODate("2013-03-05T20:05:54.676Z"),
> > > > "general" : [
> > > > {
> > > > "tickets" : [ ],
> > > > "commits" : [
> > > > {
> > > > "lines" : 1,
> > > > "number" : 1,
> > > > "language" : null
> > > > }
> > > > ],
> > > > "category" : null,
> > > > "messages" : {
> > > > "assigned" : 0,
> > > > "solved" : 0,
> > > > "totsolvingtime" : 0,
> > > > "revoked" : 0
> > > > }
> > > > }
> > > > ],
> > > > "visible" : false,
> > > > "last_login" : null
> > > > }
> > > >
> > > >
> > > > As you can see, `general.tickets` is a list, not a dict, but it's
> > defined
> > > > as a dict in the schema. Maybe you guys could track that down?
> > > >
> > > > Tim
> > > >
> > > >
> > > > On Sunday, March 3, 2013 at 4:35 AM, Stefano Invernizzi wrote:
> > > >
> > > > > Thanks Dave for your suggestion! I modified the bootstrap.py file, so
> > > > that
> > > > > when the Users neighborhood is created, our tool for userstats is
> > > >
> > > >
> > >
> >
> > set as
> > > >
> > > > an
> > > > > anchored tool, and it perfectly works. However, that way, if you do
> > > >
> > > >
> > >
> >
> > not
> > > >
> > > > run
> > > > > the bootstrap.py, you have to manually add the tool to the anchored
> > > >
> > > >
> > >
> >
> > ones.
> > > > > And this is what happens in most cases for users who don't want to
> > > > > re-initialize the forge.
> > > > >
> > > > > I was also thinking about the setting in the .ini file to enable
> > > > userstats.
> > > > > I think it doesn't make sense to disable them now that stats are
> > > > > implemented as a tool. By setting userstats.enable = false, the tool
> > > > >
> > > >
> > > >
> > >
> >
> > is
> > > > > still installed for users who were using it, therefore I think it's
> > > >
> > > >
> > > > better
> > > > > to remove this option, since it would be confusing. That way, a user
> > > >
> > > >
> > >
> >
> > who
> > > > > wants to install the forge without using userstats can simply avoid
> > > > > installing the ForgeUserStats tool. I committed this change too, but
> > > > >
> > > >
> > >
> >
> > if
> > > > >
> > > >
> > > >
> > > > you
> > > > > think it's better to think again about it, I'm open to different
> > > >
> > > >
> > > > proposals.
> > > > > Thanks again,
> > > > >
> > > > > Stefano
> > > > >
> > > > >
> > > > >
> > > > > 2013/3/2 Simone Gatti <simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com) (mailto:
> > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com)) (mailto:
> > > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com))>
> > > > >
> > > > > > Dear Dave,
> > > > > > I have changed the preference page in order to meet these requests.
> > > > > > I created two new pages to collect data about contacts and
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > availability.
> > > > > > In the preference page, over the links, it is now indicated that
> > > > >
> > > >
> > > >
> > >
> >
> > these
> > > > > > personal data are not compulsory.
> > > > > > In this way, the preference page will no more become so long due to
> > > > > >
> > > > >
> > > >
> > > >
> > > > data
> > > > > > about contacts and availability precedently inserted by the user,
> > > > >
> > > >
> > > >
> > >
> >
> > and
> > > > >
> > > >
> > > >
> > > > the
> > > > > > forms not necessary are not disclosed.
> > > > > > About general personal data, I decided to leave its original form
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > in
> > > > > >
> > > > >
> > > >
> > > >
> > > > the
> > > > > > preference page, because it has fixed size and refer to general
> > > > > > information, but I put an explicit indication that they are
> > > > > >
> > > > >
> > > >
> > > >
> > > > discretionary.
> > > > > > Please, let me know what do you think about these modifications.
> > > > > > Thanks,
> > > > > > Simone
> > > > > >
> > > > > >
> > > > > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:dave@brondsema.net) (mailto:
> > dave@brondsema.net (mailto:dave@brondsema.net)) (mailto:
> > > > dave@brondsema.net (mailto:dave@brondsema.net))>
> > > > > >
> > > > > > > Cory, I think Stefano is referring to user stats, which his
> > feature
> > > > > > branch
> > > > > > > starts collecting, not user profile data (gender, location, etc).
> > > > > > >
> > > > > > > But on the topic of user profiel data, we've had a least one
> > > > SourceForge
> > > > > > > user
> > > > > > > communicate to use that he/she thought the fields were required.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > I
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > can
> > > > > > > see how
> > > > > > > this might be inferred since they're the first thing you see on
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > the
> > > > > > > /auth/prefs/
> > > > > > > form. We might consider labelling those optional, or putting
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> > them on
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > a
> > > > > > > separate
> > > > > > > page from "subscriptions" and other sections on that page.
> > > > > > >
> > > > > > > -Dave
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > > > > Stefano,
> > > > > > > >
> > > > > > > > Could a user simply not fill in the personal info fields they
> > don't
> > > > > > wish
> > > > > > > to
> > > > > > > > share? What is the value of entering that info but then not
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > displaying
> > > > > > >
> > > > > > > it;
> > > > > > > > to encourage users to enter it if only for our edification?
> > > > > > > >
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > >
> > > > > > > > Cory
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com) (mailto:
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com)) (mailto:
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com))>
> > wrote:
> > > > > > > >
> > > > > > > > > Dear all,
> > > > > > > > >
> > > > > > > > > I recently pushed some new commits allowing a single user to
> > > > hide his
> > > > > > or
> > > > > > > > > her personal statistics. I and Simone implemented it since
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > some
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > users
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > may
> > > > > > > > > prefer not to show this data. In that case, data is still
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > available
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > for
> > > > > > > > > their personal use. However, if you think we should not allow
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > users to
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > do
> > > > > > > > > this, we can simply put it back as it was.
> > > > > > > > > As usual, we hope to get some feedbacks from you about this,
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > as
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > well
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > as
> > > > > > > > > about the rest of submitted code.
> > > > > > > > > It would be great for us if the code could be reviewed and,
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > if
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > you
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > think it
> > > > > > > > > would be useful, included on the forge before we complete the
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > thesis
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > we
> > > > > > > are
> > > > > > > > > working on.
> > > > > > > > > Thank you very much!
> > > > > > > > > Stefano
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net)
> > > > > > > http://www.brondsema.net : personal
> > > > > > > http://www.splike.com : programming
> > > > > > > <><
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> >
>
>
>
Re: User stats and organizations
Posted by Stefano Invernizzi <st...@gmail.com>.
I was not able to recreate your problem, but I realized there was an error
in the code I committed yesterday, and this error is probably the reason
why you got the reported exception. I changed it and I hope this fixed the
problem. If the issue is still there, let me know about it.
Stefano
2013/3/7 Tim Van Steenburgh <tv...@gmail.com>
> Pulled the latest changes, dropped the userstats collection, pushed a
> commit to my test repo, refreshed the commiter's stats page, and got this:
>
> File
> '/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/controllers/userstats.py',
> line 124 in index
> ret_dict['discussionpercentage'] = stats.discussionRanking()
> File
> '/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/contrib_stats.py',
> line 143 in discussionRanking
> disccontr = self.getDiscussionContribution()
> File
> '/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/contrib_stats.py',
> line 87 in getDiscussionContribution
> tot = artifact.created+artifact.modified
> TypeError: unsupported operand type(s) for +: 'NoneType' and 'NoneType'
>
>
> Tim
>
>
> On Wednesday, March 6, 2013 at 4:40 PM, Stefano Invernizzi wrote:
>
> > Yes, there was an error in the initialization of the stats object. I hope
> > it's ok now.
> > Thank you for reporting it!
> > Stefano
> >
> >
> > 2013/3/5 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> tvansteenburgh@gmail.com)>
> >
> > > Stefano & Simone,
> > >
> > > Hey guys. Have been doing some more review on Userstats today. I
> > > force-pushed a couple small changes to origin/si/5453, so make sure you
> > > pull those.
> > >
> > > I ran into an error in the stats code after pushing a commit. It was a
> > > Ming schema validation error:
> > >
> > > 208 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] File
> > >
> '/var/local/env-allura/lib/python2.7/site-packages/Ming-0.3.2dev_20121101-py2.7.egg/ming/schema.py',
> > > line 327 in _validate
> > > 209 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] raise
> > > Invalid(msg, d, None, error_dict=error_dict)
> > > 210 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] Invalid:
> > > general:[0]:messages:Not a list or tuple
> > > 211 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1]
> tickets:notdict:
> > > []
> > >
> > >
> > > Here's the mongo doc:
> > >
> > > {
> > > "_id" : ObjectId("5136502261b3b44a93a7b36f"),
> > > "lastmonth" : {
> > > "assignedtickets" : [ ],
> > > "commits" : [
> > > {
> > > "programming_languages" : [ ],
> > > "lines" : 1,
> > > "categories" : [ ],
> > > "datetime" :
> > > ISODate("2013-03-05T22:28:22.341Z")
> > > }
> > > ],
> > > "solvedtickets" : [ ],
> > > "messages" : [ ],
> > > "revokedtickets" : [ ]
> > > },
> > > "user_id" : ObjectId("510ad21c61b3b426260e7586"),
> > > "lastmonthlogins" : [ ],
> > > "tot_logins_count" : 0,
> > > "registration_date" : ISODate("2013-03-05T20:05:54.676Z"),
> > > "general" : [
> > > {
> > > "tickets" : [ ],
> > > "commits" : [
> > > {
> > > "lines" : 1,
> > > "number" : 1,
> > > "language" : null
> > > }
> > > ],
> > > "category" : null,
> > > "messages" : {
> > > "assigned" : 0,
> > > "solved" : 0,
> > > "totsolvingtime" : 0,
> > > "revoked" : 0
> > > }
> > > }
> > > ],
> > > "visible" : false,
> > > "last_login" : null
> > > }
> > >
> > >
> > > As you can see, `general.tickets` is a list, not a dict, but it's
> defined
> > > as a dict in the schema. Maybe you guys could track that down?
> > >
> > > Tim
> > >
> > >
> > > On Sunday, March 3, 2013 at 4:35 AM, Stefano Invernizzi wrote:
> > >
> > > > Thanks Dave for your suggestion! I modified the bootstrap.py file, so
> > > that
> > > > when the Users neighborhood is created, our tool for userstats is
> set as
> > >
> > > an
> > > > anchored tool, and it perfectly works. However, that way, if you do
> not
> > >
> > > run
> > > > the bootstrap.py, you have to manually add the tool to the anchored
> ones.
> > > > And this is what happens in most cases for users who don't want to
> > > > re-initialize the forge.
> > > >
> > > > I was also thinking about the setting in the .ini file to enable
> > > userstats.
> > > > I think it doesn't make sense to disable them now that stats are
> > > > implemented as a tool. By setting userstats.enable = false, the tool
> is
> > > > still installed for users who were using it, therefore I think it's
> > > >
> > >
> > > better
> > > > to remove this option, since it would be confusing. That way, a user
> who
> > > > wants to install the forge without using userstats can simply avoid
> > > > installing the ForgeUserStats tool. I committed this change too, but
> if
> > > >
> > >
> > > you
> > > > think it's better to think again about it, I'm open to different
> > >
> > > proposals.
> > > > Thanks again,
> > > >
> > > > Stefano
> > > >
> > > >
> > > >
> > > > 2013/3/2 Simone Gatti <simone.gatti88@gmail.com (mailto:
> simone.gatti88@gmail.com) (mailto:
> > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com))>
> > > >
> > > > > Dear Dave,
> > > > > I have changed the preference page in order to meet these requests.
> > > > > I created two new pages to collect data about contacts and
> > > > >
> > > >
> > > >
> > >
> > > availability.
> > > > > In the preference page, over the links, it is now indicated that
> these
> > > > > personal data are not compulsory.
> > > > > In this way, the preference page will no more become so long due to
> > > > >
> > > >
> > >
> > > data
> > > > > about contacts and availability precedently inserted by the user,
> and
> > > >
> > >
> > > the
> > > > > forms not necessary are not disclosed.
> > > > > About general personal data, I decided to leave its original form
> in
> > > > >
> > > >
> > >
> > > the
> > > > > preference page, because it has fixed size and refer to general
> > > > > information, but I put an explicit indication that they are
> > > > >
> > > >
> > >
> > > discretionary.
> > > > > Please, let me know what do you think about these modifications.
> > > > > Thanks,
> > > > > Simone
> > > > >
> > > > >
> > > > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:
> dave@brondsema.net) (mailto:
> > > dave@brondsema.net (mailto:dave@brondsema.net))>
> > > > >
> > > > > > Cory, I think Stefano is referring to user stats, which his
> feature
> > > > > branch
> > > > > > starts collecting, not user profile data (gender, location, etc).
> > > > > >
> > > > > > But on the topic of user profiel data, we've had a least one
> > > SourceForge
> > > > > > user
> > > > > > communicate to use that he/she thought the fields were required.
> I
> > > > > >
> > > > >
> > > >
> > >
> > > can
> > > > > > see how
> > > > > > this might be inferred since they're the first thing you see on
> the
> > > > > > /auth/prefs/
> > > > > > form. We might consider labelling those optional, or putting
> them on
> > > > > >
> > > > >
> > > >
> > >
> > > a
> > > > > > separate
> > > > > > page from "subscriptions" and other sections on that page.
> > > > > >
> > > > > > -Dave
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > > > Stefano,
> > > > > > >
> > > > > > > Could a user simply not fill in the personal info fields they
> don't
> > > > > wish
> > > > > > to
> > > > > > > share? What is the value of entering that info but then not
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > displaying
> > > > > >
> > > > > > it;
> > > > > > > to encourage users to enter it if only for our edification?
> > > > > > >
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > Cory
> > > > > > >
> > > > > > >
> > > > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com) (mailto:
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com))>
> wrote:
> > > > > > >
> > > > > > > > Dear all,
> > > > > > > >
> > > > > > > > I recently pushed some new commits allowing a single user to
> > > hide his
> > > > > or
> > > > > > > > her personal statistics. I and Simone implemented it since
> some
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > users
> > > > > > >
> > > > > >
> > > > > >
> > > > > > may
> > > > > > > > prefer not to show this data. In that case, data is still
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > available
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > for
> > > > > > > > their personal use. However, if you think we should not allow
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > users to
> > > > > > >
> > > > > >
> > > > > >
> > > > > > do
> > > > > > > > this, we can simply put it back as it was.
> > > > > > > > As usual, we hope to get some feedbacks from you about this,
> as
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > well
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > as
> > > > > > > > about the rest of submitted code.
> > > > > > > > It would be great for us if the code could be reviewed and,
> if
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > > you
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > think it
> > > > > > > > would be useful, included on the forge before we complete the
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > thesis
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > we
> > > > > > are
> > > > > > > > working on.
> > > > > > > > Thank you very much!
> > > > > > > > Stefano
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net)
> > > > > > http://www.brondsema.net : personal
> > > > > > http://www.splike.com : programming
> > > > > > <><
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> >
> >
> >
>
>
>
Re: User stats and organizations
Posted by Tim Van Steenburgh <tv...@gmail.com>.
Pulled the latest changes, dropped the userstats collection, pushed a commit to my test repo, refreshed the commiter's stats page, and got this:
File '/home/tvansteenburgh/tvansteenburgh-9044/forge/ForgeUserStats/forgeuserstats/controllers/userstats.py', line 124 in index
ret_dict['discussionpercentage'] = stats.discussionRanking()
File '/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/contrib_stats.py', line 143 in discussionRanking
disccontr = self.getDiscussionContribution()
File '/home/tvansteenburgh/tvansteenburgh-9044/forge/Allura/allura/model/contrib_stats.py', line 87 in getDiscussionContribution
tot = artifact.created+artifact.modified
TypeError: unsupported operand type(s) for +: 'NoneType' and 'NoneType'
Tim
On Wednesday, March 6, 2013 at 4:40 PM, Stefano Invernizzi wrote:
> Yes, there was an error in the initialization of the stats object. I hope
> it's ok now.
> Thank you for reporting it!
> Stefano
>
>
> 2013/3/5 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:tvansteenburgh@gmail.com)>
>
> > Stefano & Simone,
> >
> > Hey guys. Have been doing some more review on Userstats today. I
> > force-pushed a couple small changes to origin/si/5453, so make sure you
> > pull those.
> >
> > I ran into an error in the stats code after pushing a commit. It was a
> > Ming schema validation error:
> >
> > 208 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] File
> > '/var/local/env-allura/lib/python2.7/site-packages/Ming-0.3.2dev_20121101-py2.7.egg/ming/schema.py',
> > line 327 in _validate
> > 209 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] raise
> > Invalid(msg, d, None, error_dict=error_dict)
> > 210 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] Invalid:
> > general:[0]:messages:Not a list or tuple
> > 211 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] tickets:notdict:
> > []
> >
> >
> > Here's the mongo doc:
> >
> > {
> > "_id" : ObjectId("5136502261b3b44a93a7b36f"),
> > "lastmonth" : {
> > "assignedtickets" : [ ],
> > "commits" : [
> > {
> > "programming_languages" : [ ],
> > "lines" : 1,
> > "categories" : [ ],
> > "datetime" :
> > ISODate("2013-03-05T22:28:22.341Z")
> > }
> > ],
> > "solvedtickets" : [ ],
> > "messages" : [ ],
> > "revokedtickets" : [ ]
> > },
> > "user_id" : ObjectId("510ad21c61b3b426260e7586"),
> > "lastmonthlogins" : [ ],
> > "tot_logins_count" : 0,
> > "registration_date" : ISODate("2013-03-05T20:05:54.676Z"),
> > "general" : [
> > {
> > "tickets" : [ ],
> > "commits" : [
> > {
> > "lines" : 1,
> > "number" : 1,
> > "language" : null
> > }
> > ],
> > "category" : null,
> > "messages" : {
> > "assigned" : 0,
> > "solved" : 0,
> > "totsolvingtime" : 0,
> > "revoked" : 0
> > }
> > }
> > ],
> > "visible" : false,
> > "last_login" : null
> > }
> >
> >
> > As you can see, `general.tickets` is a list, not a dict, but it's defined
> > as a dict in the schema. Maybe you guys could track that down?
> >
> > Tim
> >
> >
> > On Sunday, March 3, 2013 at 4:35 AM, Stefano Invernizzi wrote:
> >
> > > Thanks Dave for your suggestion! I modified the bootstrap.py file, so
> > that
> > > when the Users neighborhood is created, our tool for userstats is set as
> >
> > an
> > > anchored tool, and it perfectly works. However, that way, if you do not
> >
> > run
> > > the bootstrap.py, you have to manually add the tool to the anchored ones.
> > > And this is what happens in most cases for users who don't want to
> > > re-initialize the forge.
> > >
> > > I was also thinking about the setting in the .ini file to enable
> > userstats.
> > > I think it doesn't make sense to disable them now that stats are
> > > implemented as a tool. By setting userstats.enable = false, the tool is
> > > still installed for users who were using it, therefore I think it's
> > >
> >
> > better
> > > to remove this option, since it would be confusing. That way, a user who
> > > wants to install the forge without using userstats can simply avoid
> > > installing the ForgeUserStats tool. I committed this change too, but if
> > >
> >
> > you
> > > think it's better to think again about it, I'm open to different
> >
> > proposals.
> > > Thanks again,
> > >
> > > Stefano
> > >
> > >
> > >
> > > 2013/3/2 Simone Gatti <simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com) (mailto:
> > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com))>
> > >
> > > > Dear Dave,
> > > > I have changed the preference page in order to meet these requests.
> > > > I created two new pages to collect data about contacts and
> > > >
> > >
> > >
> >
> > availability.
> > > > In the preference page, over the links, it is now indicated that these
> > > > personal data are not compulsory.
> > > > In this way, the preference page will no more become so long due to
> > > >
> > >
> >
> > data
> > > > about contacts and availability precedently inserted by the user, and
> > >
> >
> > the
> > > > forms not necessary are not disclosed.
> > > > About general personal data, I decided to leave its original form in
> > > >
> > >
> >
> > the
> > > > preference page, because it has fixed size and refer to general
> > > > information, but I put an explicit indication that they are
> > > >
> > >
> >
> > discretionary.
> > > > Please, let me know what do you think about these modifications.
> > > > Thanks,
> > > > Simone
> > > >
> > > >
> > > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:dave@brondsema.net) (mailto:
> > dave@brondsema.net (mailto:dave@brondsema.net))>
> > > >
> > > > > Cory, I think Stefano is referring to user stats, which his feature
> > > > branch
> > > > > starts collecting, not user profile data (gender, location, etc).
> > > > >
> > > > > But on the topic of user profiel data, we've had a least one
> > SourceForge
> > > > > user
> > > > > communicate to use that he/she thought the fields were required. I
> > > > >
> > > >
> > >
> >
> > can
> > > > > see how
> > > > > this might be inferred since they're the first thing you see on the
> > > > > /auth/prefs/
> > > > > form. We might consider labelling those optional, or putting them on
> > > > >
> > > >
> > >
> >
> > a
> > > > > separate
> > > > > page from "subscriptions" and other sections on that page.
> > > > >
> > > > > -Dave
> > > > >
> > > > >
> > > > >
> > > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > > Stefano,
> > > > > >
> > > > > > Could a user simply not fill in the personal info fields they don't
> > > > wish
> > > > > to
> > > > > > share? What is the value of entering that info but then not
> > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > displaying
> > > > >
> > > > > it;
> > > > > > to encourage users to enter it if only for our edification?
> > > > > >
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Cory
> > > > > >
> > > > > >
> > > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com) (mailto:
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com))> wrote:
> > > > > >
> > > > > > > Dear all,
> > > > > > >
> > > > > > > I recently pushed some new commits allowing a single user to
> > hide his
> > > > or
> > > > > > > her personal statistics. I and Simone implemented it since some
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > users
> > > > > >
> > > > >
> > > > >
> > > > > may
> > > > > > > prefer not to show this data. In that case, data is still
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> > available
> > > > > >
> > > > >
> > > >
> > > >
> > > > for
> > > > > > > their personal use. However, if you think we should not allow
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > users to
> > > > > >
> > > > >
> > > > >
> > > > > do
> > > > > > > this, we can simply put it back as it was.
> > > > > > > As usual, we hope to get some feedbacks from you about this, as
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> > well
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > as
> > > > > > > about the rest of submitted code.
> > > > > > > It would be great for us if the code could be reviewed and, if
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> > you
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > think it
> > > > > > > would be useful, included on the forge before we complete the
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> > thesis
> > > > > >
> > > > >
> > > >
> > > >
> > > > we
> > > > > are
> > > > > > > working on.
> > > > > > > Thank you very much!
> > > > > > > Stefano
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net)
> > > > > http://www.brondsema.net : personal
> > > > > http://www.splike.com : programming
> > > > > <><
> > > > >
> > > >
> > > >
> > >
> >
> >
>
>
>
Re: User stats and organizations
Posted by Stefano Invernizzi <st...@gmail.com>.
Yes, there was an error in the initialization of the stats object. I hope
it's ok now.
Thank you for reporting it!
Stefano
2013/3/5 Tim Van Steenburgh <tv...@gmail.com>
> Stefano & Simone,
>
> Hey guys. Have been doing some more review on Userstats today. I
> force-pushed a couple small changes to origin/si/5453, so make sure you
> pull those.
>
> I ran into an error in the stats code after pushing a commit. It was a
> Ming schema validation error:
>
> 208 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] File
> '/var/local/env-allura/lib/python2.7/site-packages/Ming-0.3.2dev_20121101-py2.7.egg/ming/schema.py',
> line 327 in _validate
> 209 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] raise
> Invalid(msg, d, None, error_dict=error_dict)
> 210 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] Invalid:
> general:[0]:messages:Not a list or tuple
> 211 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] tickets:notdict:
> []
>
>
> Here's the mongo doc:
>
> {
> "_id" : ObjectId("5136502261b3b44a93a7b36f"),
> "lastmonth" : {
> "assignedtickets" : [ ],
> "commits" : [
> {
> "programming_languages" : [ ],
> "lines" : 1,
> "categories" : [ ],
> "datetime" :
> ISODate("2013-03-05T22:28:22.341Z")
> }
> ],
> "solvedtickets" : [ ],
> "messages" : [ ],
> "revokedtickets" : [ ]
> },
> "user_id" : ObjectId("510ad21c61b3b426260e7586"),
> "lastmonthlogins" : [ ],
> "tot_logins_count" : 0,
> "registration_date" : ISODate("2013-03-05T20:05:54.676Z"),
> "general" : [
> {
> "tickets" : [ ],
> "commits" : [
> {
> "lines" : 1,
> "number" : 1,
> "language" : null
> }
> ],
> "category" : null,
> "messages" : {
> "assigned" : 0,
> "solved" : 0,
> "totsolvingtime" : 0,
> "revoked" : 0
> }
> }
> ],
> "visible" : false,
> "last_login" : null
> }
>
>
> As you can see, `general.tickets` is a list, not a dict, but it's defined
> as a dict in the schema. Maybe you guys could track that down?
>
> Tim
>
>
> On Sunday, March 3, 2013 at 4:35 AM, Stefano Invernizzi wrote:
>
> > Thanks Dave for your suggestion! I modified the bootstrap.py file, so
> that
> > when the Users neighborhood is created, our tool for userstats is set as
> an
> > anchored tool, and it perfectly works. However, that way, if you do not
> run
> > the bootstrap.py, you have to manually add the tool to the anchored ones.
> > And this is what happens in most cases for users who don't want to
> > re-initialize the forge.
> >
> > I was also thinking about the setting in the .ini file to enable
> userstats.
> > I think it doesn't make sense to disable them now that stats are
> > implemented as a tool. By setting userstats.enable = false, the tool is
> > still installed for users who were using it, therefore I think it's
> better
> > to remove this option, since it would be confusing. That way, a user who
> > wants to install the forge without using userstats can simply avoid
> > installing the ForgeUserStats tool. I committed this change too, but if
> you
> > think it's better to think again about it, I'm open to different
> proposals.
> > Thanks again,
> >
> > Stefano
> >
> >
> >
> > 2013/3/2 Simone Gatti <simone.gatti88@gmail.com (mailto:
> simone.gatti88@gmail.com)>
> >
> > > Dear Dave,
> > > I have changed the preference page in order to meet these requests.
> > > I created two new pages to collect data about contacts and
> availability.
> > > In the preference page, over the links, it is now indicated that these
> > > personal data are not compulsory.
> > > In this way, the preference page will no more become so long due to
> data
> > > about contacts and availability precedently inserted by the user, and
> the
> > > forms not necessary are not disclosed.
> > > About general personal data, I decided to leave its original form in
> the
> > > preference page, because it has fixed size and refer to general
> > > information, but I put an explicit indication that they are
> discretionary.
> > > Please, let me know what do you think about these modifications.
> > > Thanks,
> > > Simone
> > >
> > >
> > > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:
> dave@brondsema.net)>
> > >
> > > > Cory, I think Stefano is referring to user stats, which his feature
> > > branch
> > > > starts collecting, not user profile data (gender, location, etc).
> > > >
> > > > But on the topic of user profiel data, we've had a least one
> SourceForge
> > > > user
> > > > communicate to use that he/she thought the fields were required. I
> can
> > > > see how
> > > > this might be inferred since they're the first thing you see on the
> > > > /auth/prefs/
> > > > form. We might consider labelling those optional, or putting them on
> a
> > > > separate
> > > > page from "subscriptions" and other sections on that page.
> > > >
> > > > -Dave
> > > >
> > > >
> > > >
> > > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > > Stefano,
> > > > >
> > > > > Could a user simply not fill in the personal info fields they don't
> > > wish
> > > > to
> > > > > share? What is the value of entering that info but then not
> displaying
> > > >
> > > > it;
> > > > > to encourage users to enter it if only for our edification?
> > > > >
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Cory
> > > > >
> > > > >
> > > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com)> wrote:
> > > > >
> > > > > > Dear all,
> > > > > >
> > > > > > I recently pushed some new commits allowing a single user to
> hide his
> > > or
> > > > > > her personal statistics. I and Simone implemented it since some
> users
> > > > >
> > > >
> > > > may
> > > > > > prefer not to show this data. In that case, data is still
> available
> > > > >
> > > >
> > > >
> > >
> > > for
> > > > > > their personal use. However, if you think we should not allow
> users to
> > > > >
> > > >
> > > > do
> > > > > > this, we can simply put it back as it was.
> > > > > > As usual, we hope to get some feedbacks from you about this, as
> well
> > > > > >
> > > > >
> > > >
> > > >
> > >
> > > as
> > > > > > about the rest of submitted code.
> > > > > > It would be great for us if the code could be reviewed and, if
> you
> > > > > >
> > > > >
> > > >
> > > > think it
> > > > > > would be useful, included on the forge before we complete the
> thesis
> > > > >
> > > >
> > > >
> > >
> > > we
> > > > are
> > > > > > working on.
> > > > > > Thank you very much!
> > > > > > Stefano
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net)
> > > > http://www.brondsema.net : personal
> > > > http://www.splike.com : programming
> > > > <><
> > > >
> > >
> > >
> >
> >
> >
>
>
>
Re: User stats and organizations
Posted by Tim Van Steenburgh <tv...@gmail.com>.
Stefano & Simone,
Hey guys. Have been doing some more review on Userstats today. I force-pushed a couple small changes to origin/si/5453, so make sure you pull those.
I ran into an error in the stats code after pushing a commit. It was a Ming schema validation error:
208 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] File '/var/local/env-allura/lib/python2.7/site-packages/Ming-0.3.2dev_20121101-py2.7.egg/ming/schema.py', line 327 in _validate
209 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] raise Invalid(msg, d, None, error_dict=error_dict)
210 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] Invalid: general:[0]:messages:Not a list or tuple
211 [Tue Mar 05 22:29:05 2013] [error] [client 127.0.0.1] tickets:notdict: []
Here's the mongo doc:
{
"_id" : ObjectId("5136502261b3b44a93a7b36f"),
"lastmonth" : {
"assignedtickets" : [ ],
"commits" : [
{
"programming_languages" : [ ],
"lines" : 1,
"categories" : [ ],
"datetime" : ISODate("2013-03-05T22:28:22.341Z")
}
],
"solvedtickets" : [ ],
"messages" : [ ],
"revokedtickets" : [ ]
},
"user_id" : ObjectId("510ad21c61b3b426260e7586"),
"lastmonthlogins" : [ ],
"tot_logins_count" : 0,
"registration_date" : ISODate("2013-03-05T20:05:54.676Z"),
"general" : [
{
"tickets" : [ ],
"commits" : [
{
"lines" : 1,
"number" : 1,
"language" : null
}
],
"category" : null,
"messages" : {
"assigned" : 0,
"solved" : 0,
"totsolvingtime" : 0,
"revoked" : 0
}
}
],
"visible" : false,
"last_login" : null
}
As you can see, `general.tickets` is a list, not a dict, but it's defined as a dict in the schema. Maybe you guys could track that down?
Tim
On Sunday, March 3, 2013 at 4:35 AM, Stefano Invernizzi wrote:
> Thanks Dave for your suggestion! I modified the bootstrap.py file, so that
> when the Users neighborhood is created, our tool for userstats is set as an
> anchored tool, and it perfectly works. However, that way, if you do not run
> the bootstrap.py, you have to manually add the tool to the anchored ones.
> And this is what happens in most cases for users who don't want to
> re-initialize the forge.
>
> I was also thinking about the setting in the .ini file to enable userstats.
> I think it doesn't make sense to disable them now that stats are
> implemented as a tool. By setting userstats.enable = false, the tool is
> still installed for users who were using it, therefore I think it's better
> to remove this option, since it would be confusing. That way, a user who
> wants to install the forge without using userstats can simply avoid
> installing the ForgeUserStats tool. I committed this change too, but if you
> think it's better to think again about it, I'm open to different proposals.
> Thanks again,
>
> Stefano
>
>
>
> 2013/3/2 Simone Gatti <simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com)>
>
> > Dear Dave,
> > I have changed the preference page in order to meet these requests.
> > I created two new pages to collect data about contacts and availability.
> > In the preference page, over the links, it is now indicated that these
> > personal data are not compulsory.
> > In this way, the preference page will no more become so long due to data
> > about contacts and availability precedently inserted by the user, and the
> > forms not necessary are not disclosed.
> > About general personal data, I decided to leave its original form in the
> > preference page, because it has fixed size and refer to general
> > information, but I put an explicit indication that they are discretionary.
> > Please, let me know what do you think about these modifications.
> > Thanks,
> > Simone
> >
> >
> > 2013/2/18 Dave Brondsema <dave@brondsema.net (mailto:dave@brondsema.net)>
> >
> > > Cory, I think Stefano is referring to user stats, which his feature
> > branch
> > > starts collecting, not user profile data (gender, location, etc).
> > >
> > > But on the topic of user profiel data, we've had a least one SourceForge
> > > user
> > > communicate to use that he/she thought the fields were required. I can
> > > see how
> > > this might be inferred since they're the first thing you see on the
> > > /auth/prefs/
> > > form. We might consider labelling those optional, or putting them on a
> > > separate
> > > page from "subscriptions" and other sections on that page.
> > >
> > > -Dave
> > >
> > >
> > >
> > > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > > Stefano,
> > > >
> > > > Could a user simply not fill in the personal info fields they don't
> > wish
> > > to
> > > > share? What is the value of entering that info but then not displaying
> > >
> > > it;
> > > > to encourage users to enter it if only for our edification?
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Cory
> > > >
> > > >
> > > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > > stefano.invernizzi88@gmail.com (mailto:stefano.invernizzi88@gmail.com)> wrote:
> > > >
> > > > > Dear all,
> > > > >
> > > > > I recently pushed some new commits allowing a single user to hide his
> > or
> > > > > her personal statistics. I and Simone implemented it since some users
> > > >
> > >
> > > may
> > > > > prefer not to show this data. In that case, data is still available
> > > >
> > >
> > >
> >
> > for
> > > > > their personal use. However, if you think we should not allow users to
> > > >
> > >
> > > do
> > > > > this, we can simply put it back as it was.
> > > > > As usual, we hope to get some feedbacks from you about this, as well
> > > > >
> > > >
> > >
> > >
> >
> > as
> > > > > about the rest of submitted code.
> > > > > It would be great for us if the code could be reviewed and, if you
> > > > >
> > > >
> > >
> > > think it
> > > > > would be useful, included on the forge before we complete the thesis
> > > >
> > >
> > >
> >
> > we
> > > are
> > > > > working on.
> > > > > Thank you very much!
> > > > > Stefano
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > > --
> > > Dave Brondsema : dave@brondsema.net (mailto:dave@brondsema.net)
> > > http://www.brondsema.net : personal
> > > http://www.splike.com : programming
> > > <><
> > >
> >
> >
>
>
>
Re: User stats and organizations
Posted by Stefano Invernizzi <st...@gmail.com>.
Thanks Dave for your suggestion! I modified the bootstrap.py file, so that
when the Users neighborhood is created, our tool for userstats is set as an
anchored tool, and it perfectly works. However, that way, if you do not run
the bootstrap.py, you have to manually add the tool to the anchored ones.
And this is what happens in most cases for users who don't want to
re-initialize the forge.
I was also thinking about the setting in the .ini file to enable userstats.
I think it doesn't make sense to disable them now that stats are
implemented as a tool. By setting userstats.enable = false, the tool is
still installed for users who were using it, therefore I think it's better
to remove this option, since it would be confusing. That way, a user who
wants to install the forge without using userstats can simply avoid
installing the ForgeUserStats tool. I committed this change too, but if you
think it's better to think again about it, I'm open to different proposals.
Thanks again,
Stefano
2013/3/2 Simone Gatti <si...@gmail.com>
> Dear Dave,
> I have changed the preference page in order to meet these requests.
> I created two new pages to collect data about contacts and availability.
> In the preference page, over the links, it is now indicated that these
> personal data are not compulsory.
> In this way, the preference page will no more become so long due to data
> about contacts and availability precedently inserted by the user, and the
> forms not necessary are not disclosed.
> About general personal data, I decided to leave its original form in the
> preference page, because it has fixed size and refer to general
> information, but I put an explicit indication that they are discretionary.
> Please, let me know what do you think about these modifications.
> Thanks,
> Simone
>
>
> 2013/2/18 Dave Brondsema <da...@brondsema.net>
>
> > Cory, I think Stefano is referring to user stats, which his feature
> branch
> > starts collecting, not user profile data (gender, location, etc).
> >
> > But on the topic of user profiel data, we've had a least one SourceForge
> > user
> > communicate to use that he/she thought the fields were required. I can
> > see how
> > this might be inferred since they're the first thing you see on the
> > /auth/prefs/
> > form. We might consider labelling those optional, or putting them on a
> > separate
> > page from "subscriptions" and other sections on that page.
> >
> > -Dave
> >
> >
> >
> > On 2/18/13 9:55 AM, Cory Johns wrote:
> > > Stefano,
> > >
> > > Could a user simply not fill in the personal info fields they don't
> wish
> > to
> > > share? What is the value of entering that info but then not displaying
> > it;
> > > to encourage users to enter it if only for our edification?
> > >
> > >
> > > Thanks,
> > >
> > > Cory
> > >
> > >
> > > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > > stefano.invernizzi88@gmail.com> wrote:
> > >
> > >> Dear all,
> > >>
> > >> I recently pushed some new commits allowing a single user to hide his
> or
> > >> her personal statistics. I and Simone implemented it since some users
> > may
> > >> prefer not to show this data. In that case, data is still available
> for
> > >> their personal use. However, if you think we should not allow users to
> > do
> > >> this, we can simply put it back as it was.
> > >> As usual, we hope to get some feedbacks from you about this, as well
> as
> > >> about the rest of submitted code.
> > >> It would be great for us if the code could be reviewed and, if you
> > think it
> > >> would be useful, included on the forge before we complete the thesis
> we
> > are
> > >> working on.
> > >> Thank you very much!
> > >> Stefano
> > >>
> >
> >
> >
> > --
> > Dave Brondsema : dave@brondsema.net
> > http://www.brondsema.net : personal
> > http://www.splike.com : programming
> > <><
> >
>
Re: User stats and organizations
Posted by Simone Gatti <si...@gmail.com>.
Dear all,
I have finished working on the last modifications presented. You can find
the patch in attachment here<https://sourceforge.net/p/allura/tickets/5909/>
.
Regards, Simone
2013/3/2 Simone Gatti <si...@gmail.com>
> Dear Dave,
> I have changed the preference page in order to meet these requests.
> I created two new pages to collect data about contacts and availability.
> In the preference page, over the links, it is now indicated that these
> personal data are not compulsory.
> In this way, the preference page will no more become so long due to data
> about contacts and availability precedently inserted by the user, and the
> forms not necessary are not disclosed.
> About general personal data, I decided to leave its original form in the
> preference page, because it has fixed size and refer to general
> information, but I put an explicit indication that they are discretionary.
> Please, let me know what do you think about these modifications.
> Thanks,
> Simone
>
>
> 2013/2/18 Dave Brondsema <da...@brondsema.net>
>
>> Cory, I think Stefano is referring to user stats, which his feature branch
>> starts collecting, not user profile data (gender, location, etc).
>>
>> But on the topic of user profiel data, we've had a least one SourceForge
>> user
>> communicate to use that he/she thought the fields were required. I can
>> see how
>> this might be inferred since they're the first thing you see on the
>> /auth/prefs/
>> form. We might consider labelling those optional, or putting them on a
>> separate
>> page from "subscriptions" and other sections on that page.
>>
>> -Dave
>>
>>
>>
>> On 2/18/13 9:55 AM, Cory Johns wrote:
>> > Stefano,
>> >
>> > Could a user simply not fill in the personal info fields they don't
>> wish to
>> > share? What is the value of entering that info but then not displaying
>> it;
>> > to encourage users to enter it if only for our edification?
>> >
>> >
>> > Thanks,
>> >
>> > Cory
>> >
>> >
>> > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
>> > stefano.invernizzi88@gmail.com> wrote:
>> >
>> >> Dear all,
>> >>
>> >> I recently pushed some new commits allowing a single user to hide his
>> or
>> >> her personal statistics. I and Simone implemented it since some users
>> may
>> >> prefer not to show this data. In that case, data is still available for
>> >> their personal use. However, if you think we should not allow users to
>> do
>> >> this, we can simply put it back as it was.
>> >> As usual, we hope to get some feedbacks from you about this, as well as
>> >> about the rest of submitted code.
>> >> It would be great for us if the code could be reviewed and, if you
>> think it
>> >> would be useful, included on the forge before we complete the thesis
>> we are
>> >> working on.
>> >> Thank you very much!
>> >> Stefano
>> >>
>>
>>
>>
>> --
>> Dave Brondsema : dave@brondsema.net
>> http://www.brondsema.net : personal
>> http://www.splike.com : programming
>> <><
>>
>
>
Re: User stats and organizations
Posted by Simone Gatti <si...@gmail.com>.
Dear Dave,
I have changed the preference page in order to meet these requests.
I created two new pages to collect data about contacts and availability.
In the preference page, over the links, it is now indicated that these
personal data are not compulsory.
In this way, the preference page will no more become so long due to data
about contacts and availability precedently inserted by the user, and the
forms not necessary are not disclosed.
About general personal data, I decided to leave its original form in the
preference page, because it has fixed size and refer to general
information, but I put an explicit indication that they are discretionary.
Please, let me know what do you think about these modifications.
Thanks,
Simone
2013/2/18 Dave Brondsema <da...@brondsema.net>
> Cory, I think Stefano is referring to user stats, which his feature branch
> starts collecting, not user profile data (gender, location, etc).
>
> But on the topic of user profiel data, we've had a least one SourceForge
> user
> communicate to use that he/she thought the fields were required. I can
> see how
> this might be inferred since they're the first thing you see on the
> /auth/prefs/
> form. We might consider labelling those optional, or putting them on a
> separate
> page from "subscriptions" and other sections on that page.
>
> -Dave
>
>
>
> On 2/18/13 9:55 AM, Cory Johns wrote:
> > Stefano,
> >
> > Could a user simply not fill in the personal info fields they don't wish
> to
> > share? What is the value of entering that info but then not displaying
> it;
> > to encourage users to enter it if only for our edification?
> >
> >
> > Thanks,
> >
> > Cory
> >
> >
> > On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> > stefano.invernizzi88@gmail.com> wrote:
> >
> >> Dear all,
> >>
> >> I recently pushed some new commits allowing a single user to hide his or
> >> her personal statistics. I and Simone implemented it since some users
> may
> >> prefer not to show this data. In that case, data is still available for
> >> their personal use. However, if you think we should not allow users to
> do
> >> this, we can simply put it back as it was.
> >> As usual, we hope to get some feedbacks from you about this, as well as
> >> about the rest of submitted code.
> >> It would be great for us if the code could be reviewed and, if you
> think it
> >> would be useful, included on the forge before we complete the thesis we
> are
> >> working on.
> >> Thank you very much!
> >> Stefano
> >>
>
>
>
> --
> Dave Brondsema : dave@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
Re: User stats and organizations
Posted by Dave Brondsema <da...@brondsema.net>.
Cory, I think Stefano is referring to user stats, which his feature branch
starts collecting, not user profile data (gender, location, etc).
But on the topic of user profiel data, we've had a least one SourceForge user
communicate to use that he/she thought the fields were required. I can see how
this might be inferred since they're the first thing you see on the /auth/prefs/
form. We might consider labelling those optional, or putting them on a separate
page from "subscriptions" and other sections on that page.
-Dave
On 2/18/13 9:55 AM, Cory Johns wrote:
> Stefano,
>
> Could a user simply not fill in the personal info fields they don't wish to
> share? What is the value of entering that info but then not displaying it;
> to encourage users to enter it if only for our edification?
>
>
> Thanks,
>
> Cory
>
>
> On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
> stefano.invernizzi88@gmail.com> wrote:
>
>> Dear all,
>>
>> I recently pushed some new commits allowing a single user to hide his or
>> her personal statistics. I and Simone implemented it since some users may
>> prefer not to show this data. In that case, data is still available for
>> their personal use. However, if you think we should not allow users to do
>> this, we can simply put it back as it was.
>> As usual, we hope to get some feedbacks from you about this, as well as
>> about the rest of submitted code.
>> It would be great for us if the code could be reviewed and, if you think it
>> would be useful, included on the forge before we complete the thesis we are
>> working on.
>> Thank you very much!
>> Stefano
>>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: User stats and organizations
Posted by Cory Johns <jo...@geek.net>.
Stefano,
Could a user simply not fill in the personal info fields they don't wish to
share? What is the value of entering that info but then not displaying it;
to encourage users to enter it if only for our edification?
Thanks,
Cory
On Sat, Feb 16, 2013 at 9:53 AM, Stefano Invernizzi <
stefano.invernizzi88@gmail.com> wrote:
> Dear all,
>
> I recently pushed some new commits allowing a single user to hide his or
> her personal statistics. I and Simone implemented it since some users may
> prefer not to show this data. In that case, data is still available for
> their personal use. However, if you think we should not allow users to do
> this, we can simply put it back as it was.
> As usual, we hope to get some feedbacks from you about this, as well as
> about the rest of submitted code.
> It would be great for us if the code could be reviewed and, if you think it
> would be useful, included on the forge before we complete the thesis we are
> working on.
> Thank you very much!
> Stefano
>
>
> 2013/2/2 Stefano Invernizzi <st...@gmail.com>
>
> > Hi,
> > Yes, you are right! I changed the name of the parameter in the
> > configuration file, but I forgot to do the same in the test.ini file,
> > therefore all our tests resulted in errors or failures. I changed the
> > parameter in that file and now it looks like everything is ok. I'm sorry
> > about that.
> >
> > Stefano
> >
> >
> > 2013/2/1 Tim Van Steenburgh <tv...@gmail.com>
> >
> >> Hey guys,
> >>
> >> I've started to look at this again. Getting several errors and failures
> >> running `nosetests` in ForgeUserStats. Can you look into that?
> >>
> >> Tim
> >>
> >>
> >> On Wednesday, January 30, 2013 at 2:17 PM, Tim Van Steenburgh wrote:
> >>
> >> > Thanks guys! I'm in the middle of another code review at the moment,
> >> but I'll take a look soon.
> >> >
> >> > Tim
> >> >
> >> > On Wednesday, January 30, 2013 at 12:36 PM, Stefano Invernizzi wrote:
> >> >
> >> > > Dear Tim,
> >> > > After fixing the issues you reported in your first review, we also
> >> fixed
> >> > > other things today and we committed them to the repository.
> >> > > We hope this improves our code. We also implemented the loop to
> >> register
> >> > > additional listeners, as I had explained in the discussion of the
> >> ticket a
> >> > > few days ago. Particularly, we forced the parameter in the
> >> configuration
> >> > > file to be the equal to the entry point name, followed by ".enable",
> >> so
> >> > > that the whole mechanism can be easily extended.
> >> > > Let us know what you think about this additional commits and if
> there
> >> other
> >> > > things to be improved. Thank you again for your review!
> >> > >
> >> > > Stefano & Simone
> >> > >
> >> > >
> >> > > 2013/1/18 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> >> tvansteenburgh@gmail.com)>
> >> > >
> >> > > > Stefano & Simone,
> >> > > >
> >> > > > I've posted a first review of the User stats code on
> >> > > > https://sourceforge.net/p/allura/tickets/5453/.
> >> > > >
> >> > > > Tim Van Steenburgh
> >> > > >
> >> > > >
> >> > > >
> >> > > > On Wednesday, January 9, 2013 at 11:30 PM, Tim Van Steenburgh
> wrote:
> >> > > >
> >> > > > > Hi Stefano & Simone,
> >> > > > >
> >> > > > > Sorry for the delay, a lot of us were on extended vacation for
> the
> >> > > > Christmas holiday. I've begun looking at your branch and intend to
> >> provide
> >> > > > some feedback in the near future. Thanks for your contribution to
> >> Allura!
> >> > > > >
> >> > > > > Tim Van Steenburgh
> >> > > > >
> >> > > > >
> >> > > > > On Wednesday, January 9, 2013 at 4:14 AM, Stefano Invernizzi
> >> wrote:
> >> > > > >
> >> > > > > > Dear all,
> >> > > > > >
> >> > > > > > We still didn't get any feedback about the uploaded code.
> >> Please, let
> >> > > > us
> >> > > > > > know what you think about it and if there's something we can
> >> improve.
> >> > > > > >
> >> > > > > > Regards,
> >> > > > > >
> >> > > > > > Simone & Stefano
> >> > > > > >
> >> > > > > >
> >> > > > > > 2012/12/13 Stefano Invernizzi <stefano.invernizzi88@gmail.com
> (mailto:
> >> stefano.invernizzi88@gmail.com) (mailto:
> >> > > > stefano.invernizzi88@gmail.com (mailto:
> >> stefano.invernizzi88@gmail.com))>
> >> > > > > >
> >> > > > > > > Dear all,
> >> > > > > > > Since yesterday the code is available on the repository. As
> >> > > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > suggested in
> >> > > > > > > the proposed code contributors policy, I created a new
> branch
> >> named
> >> > > > > > > si/5453. Feel free to comment our work, and send feedbacks
> or
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > suggestions
> >> > > > > > > about possible improvements.
> >> > > > > > >
> >> > > > > > > Stefano & Simone
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > 2012/12/11 Simone Gatti <simone.gatti88@gmail.com (mailto:
> >> simone.gatti88@gmail.com) (mailto:
> >> > > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com))>
> >> > > > > > >
> >> > > > > > > > Dear all,
> >> > > > > > > >
> >> > > > > > > > thank you for your feedback!!
> >> > > > > > > > First of all, in the next hours we'll create a branch with
> >> the
> >> > > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > extension
> >> > > > > > > > of
> >> > > > > > > > UserStats, so that you can see our code to discuss it and
> >> its
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > possible
> >> > > > > > > > improvements. After that we'll upload the extensions of
> the
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > Organization
> >> > > > > > > > and OrganizationStats.
> >> > > > > > > > About the possibility to define an organization based on a
> >> shared
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > topic of
> >> > > > > > > > interest, we have not considered it. We assumed that the
> >> kind of
> >> > > > > > > > organization could be: "for-profit business", "foundation
> >> or other
> >> > > > > > > > non-profit organization" or "research and/or education
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > institution", like
> >> > > > > > > > the organizations in the real world. We don't know if the
> >> concept
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > is the
> >> > > > > > > > same, in that case we can easily add a new type of
> >> organization.
> >> > > > > > > > (e.g."group of interest").
> >> > > > > > > > As for Rich's proposal it's a great idea! We have
> >> considered it
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > but we
> >> > > > > > > > later decided to focus on other aspects in our thesis.
> >> Anyway it's
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > the
> >> > > > > > > > best
> >> > > > > > > > way to use the additional data included in the profile.
> >> > > > > > > > I don't have commit access on the repository to upload my
> >> code.
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > Since we
> >> > > > > > > > developed it together, Stefano will commit it.
> >> > > > > > > >
> >> > > > > > > > Regards,
> >> > > > > > > >
> >> > > > > > > > Simone.
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > 2012/12/10 Alvaro del Castillo <acs@bitergia.com (mailto:
> >> acs@bitergia.com) (mailto:
> >> > > > acs@bitergia.com (mailto:acs@bitergia.com))>
> >> > > > > > > >
> >> > > > > > > > > Dear Simone,
> >> > > > > > > > >
> >> > > > > > > > > First of all, I am sorry about the delayed response.
> >> > > > > > > > >
> >> > > > > > > > > El jue, 29-11-2012 a las 19:06 +0100, Simone Gatti
> >> escribió:
> >> > > > > > > > > > Dear all,
> >> > > > > > > > > >
> >> > > > > > > > > > During the last weeks, while discussing our work on
> >> including
> >> > > > new
> >> > > > > > > > details
> >> > > > > > > > > > in users' profiles on the forge, I and Stefano
> >> Invernizzi also
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > continued
> >> > > > > > > > > > working on the other features we introduced in one of
> >> our first
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > messages
> >> > > > > > > > > on
> >> > > > > > > > > > the mailing list, back in July.
> >> > > > > > > > > > Now we have completed the implementation of these
> >> tools, and
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > we would
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > like
> >> > > > > > > > > > to get feedbacks from you in order to check if it's
> >> possible to
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > include
> >> > > > > > > > > > them on the Allura platform.
> >> > > > > > > > > >
> >> > > > > > > > > > The additional features we implemented consist of two
> >> main
> >> > > > parts.
> >> > > > > > > > First
> >> > > > > > > > > of
> >> > > > > > > > > > all, we included the concept of organization, namely
> >> companies,
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > foundations
> >> > > > > > > > > > or other non-profit organizations and research and
> >> education
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > institutions.
> >> > > > > > > > > > Each organization is now allowed to create a profile,
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > including some
> >> > > > > > > > > > details about it, like a description, its working
> >> fields, its
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > size,
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > etc...
> >> > > > > > > > > > . Moreover, users can be linked to the organizations
> >> they
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > belong to,
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > and
> >> > > > > > > > > > projects can be linked to the organizations developing
> >> them.
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > For both
> >> > > > > > > > >
> >> > > > > > > > > these
> >> > > > > > > > > > kinds of relationships, we implemented a two-way
> >> mechanism:
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > the user
> >> > > > > > > > > > requests to be registered as a member of the
> >> organization and
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > the
> >> > > > > > > > > > organization has to confirm it, or vice-versa.
> >> Similarly, an
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > organization
> >> > > > > > > > > > sends a request to be listed as the developer of a
> >> project,
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > and the
> >> > > > > > > > > > administrator of the project has to accept it, or
> >> vice-versa.
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > When a
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > user
> >> > > > > > > > > > leaves an organization, he can set this on the forge,
> >> and the
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > enrollment
> >> > > > > > > > > in
> >> > > > > > > > > > this organization will be shown as a past membership.
> >> The same
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > applies
> >> > > > > > > > >
> >> > > > > > > > > for
> >> > > > > > > > > > project collaborations: an organization can freely
> set a
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > collaboration
> >> > > > > > > > > > within a project as completed, because the
> organization
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > doesn't want
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > to
> >> > > > > > > > > > continue working on the project, and it will be shown
> >> as a past
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > involvement.
> >> > > > > > > > > > We believe this features could be very useful on a
> >> forge which
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > is
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > used by
> >> > > > > > > > > > more than one organization, because it allows to have
> a
> >> better
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > awareness
> >> > > > > > > > > of
> >> > > > > > > > > > the community, knowing how users working on a project
> >> are
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > organized in
> >> > > > > > > > >
> >> > > > > > > > > the
> >> > > > > > > > > > real life. It can also increase trust for those
> projects
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > developed by
> >> > > > > > > > > > well-known organizations.
> >> > > > > > > > > >
> >> > > > > > > > > > The second feature we developed is related to users,
> and
> >> > > > consits of a
> >> > > > > > > > set
> >> > > > > > > > > > of metrics gathered from their activity.
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > This is a really interesting thing for me!
> >> > > > > > > > >
> >> > > > > > > > > > These metrics include the number
> >> > > > > > > > > > of created or modified artifacts (also separated for
> >> different
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > kinds
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > of
> >> > > > > > > > > > artifacts), the number of assigned tickets, solved
> >> tickets and
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > "revoked"
> >> > > > > > > > > > tickets, namely tickets which were assigned to a user
> >> but
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > whose owner
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > was
> >> > > > > > > > > > later changed. Moreover, the number of commits is
> >> collected,
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > together
> >> > > > > > > > >
> >> > > > > > > > > with
> >> > > > > > > > > > the total number of added or modified lines of code by
> >> the
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > user. For a
> >> > > > > > > > > > certain user, all these metrics are shown on a page on
> >> the
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > form, as a
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > total
> >> > > > > > > > > > value since the user's registration, as well as an
> >> average
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > per-month
> >> > > > > > > > >
> >> > > > > > > > > value.
> >> > > > > > > > > > The metrics are also calculated considering the last
> 30
> >> days
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > only, in
> >> > > > > > > > >
> >> > > > > > > > > order
> >> > > > > > > > > > to allow to check whether the user is still active on
> >> the
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > forge or
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > not,
> >> > > > > > > > > and
> >> > > > > > > > > > if he is increasing his efforts on the forge or not.
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > Is this code already available?
> >> > > > > > > > >
> >> > > > > > > > > In Bitergia our main focus is analyzing software
> projects
> >> using
> >> > > > metrics
> >> > > > > > > > > and we are integrating some of our tools in Allura. We
> >> are using
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > a
> >> > > > > > > > > different approach from you, getting the metrics from a
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > consolidated
> >> > > > > > > > > database that gathers the data from Allura, but at the
> >> end, the
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > metrics
> >> > > > > > > > > are really similar.
> >> > > > > > > > >
> >> > > > > > > > > We are working in different kind of visualization also,
> >> so we
> >> > > > can share
> >> > > > > > > > > also here experiences.
> >> > > > > > > > >
> >> > > > > > > > > > Moreover, it is also possible to see these values for
> a
> >> single
> >> > > > > > > > category
> >> > > > > > > > > > only, namely considering all the data regarding
> projects
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > tagged as
> >> > > > > > > > > > belonging to that category. A graph showing the number
> >> of
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > joined
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > projects
> >> > > > > > > > > > by the user for each category is also shown, to
> >> highlight the
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > kind of
> >> > > > > > > > > > applications the user is focused on.
> >> > > > > > > > > > Finally, the previously listed statistics are also
> >> calculated
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > for
> >> > > > > > > > > > organizations, by considering the activity of the
> users
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > enrolled in
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > the
> >> > > > > > > > > > organization itself. Particularly, since each user can
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > possibly work
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > for
> >> > > > > > > > > > more than one organization on the forge, as well as
> >> working as
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > an
> >> > > > > > > > > > individual programmer, organizations' statistics are
> >> calculated
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > considering
> >> > > > > > > > > > only those activities performed by its members on
> >> projects to
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > which
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > the
> >> > > > > > > > > > organizatione is explicitely involved.
> >> > > > > > > > > > We think these features are useful to allow users to
> >> have a
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > deeper
> >> > > > > > > > > > awareness of someone else's experience and interests,
> >> and this
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > could
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > also
> >> > > > > > > > > > help in identifying partners for a certain project.
> >> > > > > > > > > >
> >> > > > > > > > > > These features are implemented as external features
> and
> >> can be
> >> > > > easily
> >> > > > > > > > > > enabled or disabled by setting boolean parameters in
> >> the .ini
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > file.
> >> > > > > > > > > > Therefore, it is possible to enable organizations
> only,
> >> without
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > including
> >> > > > > > > > > > the statistics features, or including statistics for
> >> users
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > only, and
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > so
> >> > > > > > > > > on.
> >> > > > > > > > > > Of course, it is not possible to enable organization
> >> statistics
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > without
> >> > > > > > > > > > enabling the concept of organization on the forge.
> >> > > > > > > > > >
> >> > > > > > > > > > We would like to know what you think about these
> >> features, and
> >> > > > we
> >> > > > > > > > would
> >> > > > > > > > > > like to know how we can provide you our code to get a
> >> feedback
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > from
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > you
> >> > > > > > > > > > and, eventually, to discuss improvements and changes
> on
> >> it.
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > I think it is a really good use case por the code
> >> contributors
> >> > > > policy
> >> > > > > > > > > proposed in the mailing list.
> >> > > > > > > > >
> >> > > > > > > > > > Stefano is now
> >> > > > > > > > > > allowed to write on the repositoy, but since I am not
> >> allowed
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > to do
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > so,
> >> > > > > > > > > and
> >> > > > > > > > > > since these features should obviously be discussed
> >> before being
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > included
> >> > > > > > > > > on
> >> > > > > > > > > > the project, I don't know if working there, even on a
> >> new
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > branch, is
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > the
> >> > > > > > > > > > best solution.
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > I think so. Create a new experimental branch and upload
> >> the code
> >> > > > to
> >> > > > > > > > > Allura so for others developers like me, it is easy to
> >> start
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > playing
> >> > > > > > > > > with it.
> >> > > > > > > > >
> >> > > > > > > > > Cheers
> >> > > > > > > > >
> >> > > > > > > > > > Also, let us know if you prefer to check the two
> >> features
> >> > > > > > > > > > separately or not. Probably, it would be easier to do
> it
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > incrementally,
> >> > > > > > > > > > considering one of them at a time.
> >> > > > > > > > > >
> >> > > > > > > > > > Regards,
> >> > > > > > > > > >
> >> > > > > > > > > > Simone Gatti and Stefano Invernizzi
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > --
> >> > > > > > > > > |\_____/| Alvaro del Castillo
> >> > > > > > > > > [o] [o] acs@bitergia.com (mailto:acs@bitergia.com)
> >> (mailto:acs@bitergia.com) - CTO,
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > Software Engineer
> >> > > > > > > > > | V | http://www.bitergia.com
> >> > > > > > > > > | |
> >> > > > > > > > > -ooo-ooo-
> >> > > > > > > > > |\_____/| Alvaro del Castillo
> >> > > > > > > > > [o] [o] acs@bitergia.com (mailto:acs@bitergia.com)
> >> (mailto:acs@bitergia.com) - CTO,
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > > Software Engineer
> >> > > > > > > > > | V | http://www.bitergia.com
> >> > > > > > > > > | |
> >> > > > > > > > > -ooo-ooo-
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >
>
--
====
This e- mail message is intended only for the named recipient(s) above. It
may contain confidential and privileged information. If you are not the
intended recipient you are hereby notified that any dissemination,
distribution or copying of this e-mail and any attachment(s) is strictly
prohibited. If you have received this e-mail in error, please immediately
notify the sender by replying to this e-mail and delete the message and any
attachment(s) from your system. Thank you.
Re: User stats and organizations
Posted by Stefano Invernizzi <st...@gmail.com>.
Dear all,
I recently pushed some new commits allowing a single user to hide his or
her personal statistics. I and Simone implemented it since some users may
prefer not to show this data. In that case, data is still available for
their personal use. However, if you think we should not allow users to do
this, we can simply put it back as it was.
As usual, we hope to get some feedbacks from you about this, as well as
about the rest of submitted code.
It would be great for us if the code could be reviewed and, if you think it
would be useful, included on the forge before we complete the thesis we are
working on.
Thank you very much!
Stefano
2013/2/2 Stefano Invernizzi <st...@gmail.com>
> Hi,
> Yes, you are right! I changed the name of the parameter in the
> configuration file, but I forgot to do the same in the test.ini file,
> therefore all our tests resulted in errors or failures. I changed the
> parameter in that file and now it looks like everything is ok. I'm sorry
> about that.
>
> Stefano
>
>
> 2013/2/1 Tim Van Steenburgh <tv...@gmail.com>
>
>> Hey guys,
>>
>> I've started to look at this again. Getting several errors and failures
>> running `nosetests` in ForgeUserStats. Can you look into that?
>>
>> Tim
>>
>>
>> On Wednesday, January 30, 2013 at 2:17 PM, Tim Van Steenburgh wrote:
>>
>> > Thanks guys! I'm in the middle of another code review at the moment,
>> but I'll take a look soon.
>> >
>> > Tim
>> >
>> > On Wednesday, January 30, 2013 at 12:36 PM, Stefano Invernizzi wrote:
>> >
>> > > Dear Tim,
>> > > After fixing the issues you reported in your first review, we also
>> fixed
>> > > other things today and we committed them to the repository.
>> > > We hope this improves our code. We also implemented the loop to
>> register
>> > > additional listeners, as I had explained in the discussion of the
>> ticket a
>> > > few days ago. Particularly, we forced the parameter in the
>> configuration
>> > > file to be the equal to the entry point name, followed by ".enable",
>> so
>> > > that the whole mechanism can be easily extended.
>> > > Let us know what you think about this additional commits and if there
>> other
>> > > things to be improved. Thank you again for your review!
>> > >
>> > > Stefano & Simone
>> > >
>> > >
>> > > 2013/1/18 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
>> tvansteenburgh@gmail.com)>
>> > >
>> > > > Stefano & Simone,
>> > > >
>> > > > I've posted a first review of the User stats code on
>> > > > https://sourceforge.net/p/allura/tickets/5453/.
>> > > >
>> > > > Tim Van Steenburgh
>> > > >
>> > > >
>> > > >
>> > > > On Wednesday, January 9, 2013 at 11:30 PM, Tim Van Steenburgh wrote:
>> > > >
>> > > > > Hi Stefano & Simone,
>> > > > >
>> > > > > Sorry for the delay, a lot of us were on extended vacation for the
>> > > > Christmas holiday. I've begun looking at your branch and intend to
>> provide
>> > > > some feedback in the near future. Thanks for your contribution to
>> Allura!
>> > > > >
>> > > > > Tim Van Steenburgh
>> > > > >
>> > > > >
>> > > > > On Wednesday, January 9, 2013 at 4:14 AM, Stefano Invernizzi
>> wrote:
>> > > > >
>> > > > > > Dear all,
>> > > > > >
>> > > > > > We still didn't get any feedback about the uploaded code.
>> Please, let
>> > > > us
>> > > > > > know what you think about it and if there's something we can
>> improve.
>> > > > > >
>> > > > > > Regards,
>> > > > > >
>> > > > > > Simone & Stefano
>> > > > > >
>> > > > > >
>> > > > > > 2012/12/13 Stefano Invernizzi <stefano.invernizzi88@gmail.com(mailto:
>> stefano.invernizzi88@gmail.com) (mailto:
>> > > > stefano.invernizzi88@gmail.com (mailto:
>> stefano.invernizzi88@gmail.com))>
>> > > > > >
>> > > > > > > Dear all,
>> > > > > > > Since yesterday the code is available on the repository. As
>> > > > > > >
>> > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > suggested in
>> > > > > > > the proposed code contributors policy, I created a new branch
>> named
>> > > > > > > si/5453. Feel free to comment our work, and send feedbacks or
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > suggestions
>> > > > > > > about possible improvements.
>> > > > > > >
>> > > > > > > Stefano & Simone
>> > > > > > >
>> > > > > > >
>> > > > > > > 2012/12/11 Simone Gatti <simone.gatti88@gmail.com (mailto:
>> simone.gatti88@gmail.com) (mailto:
>> > > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com))>
>> > > > > > >
>> > > > > > > > Dear all,
>> > > > > > > >
>> > > > > > > > thank you for your feedback!!
>> > > > > > > > First of all, in the next hours we'll create a branch with
>> the
>> > > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > extension
>> > > > > > > > of
>> > > > > > > > UserStats, so that you can see our code to discuss it and
>> its
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > possible
>> > > > > > > > improvements. After that we'll upload the extensions of the
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > Organization
>> > > > > > > > and OrganizationStats.
>> > > > > > > > About the possibility to define an organization based on a
>> shared
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > topic of
>> > > > > > > > interest, we have not considered it. We assumed that the
>> kind of
>> > > > > > > > organization could be: "for-profit business", "foundation
>> or other
>> > > > > > > > non-profit organization" or "research and/or education
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > institution", like
>> > > > > > > > the organizations in the real world. We don't know if the
>> concept
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > is the
>> > > > > > > > same, in that case we can easily add a new type of
>> organization.
>> > > > > > > > (e.g."group of interest").
>> > > > > > > > As for Rich's proposal it's a great idea! We have
>> considered it
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > but we
>> > > > > > > > later decided to focus on other aspects in our thesis.
>> Anyway it's
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > the
>> > > > > > > > best
>> > > > > > > > way to use the additional data included in the profile.
>> > > > > > > > I don't have commit access on the repository to upload my
>> code.
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > Since we
>> > > > > > > > developed it together, Stefano will commit it.
>> > > > > > > >
>> > > > > > > > Regards,
>> > > > > > > >
>> > > > > > > > Simone.
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > 2012/12/10 Alvaro del Castillo <acs@bitergia.com (mailto:
>> acs@bitergia.com) (mailto:
>> > > > acs@bitergia.com (mailto:acs@bitergia.com))>
>> > > > > > > >
>> > > > > > > > > Dear Simone,
>> > > > > > > > >
>> > > > > > > > > First of all, I am sorry about the delayed response.
>> > > > > > > > >
>> > > > > > > > > El jue, 29-11-2012 a las 19:06 +0100, Simone Gatti
>> escribió:
>> > > > > > > > > > Dear all,
>> > > > > > > > > >
>> > > > > > > > > > During the last weeks, while discussing our work on
>> including
>> > > > new
>> > > > > > > > details
>> > > > > > > > > > in users' profiles on the forge, I and Stefano
>> Invernizzi also
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > continued
>> > > > > > > > > > working on the other features we introduced in one of
>> our first
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > messages
>> > > > > > > > > on
>> > > > > > > > > > the mailing list, back in July.
>> > > > > > > > > > Now we have completed the implementation of these
>> tools, and
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > we would
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > like
>> > > > > > > > > > to get feedbacks from you in order to check if it's
>> possible to
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > include
>> > > > > > > > > > them on the Allura platform.
>> > > > > > > > > >
>> > > > > > > > > > The additional features we implemented consist of two
>> main
>> > > > parts.
>> > > > > > > > First
>> > > > > > > > > of
>> > > > > > > > > > all, we included the concept of organization, namely
>> companies,
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > foundations
>> > > > > > > > > > or other non-profit organizations and research and
>> education
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > institutions.
>> > > > > > > > > > Each organization is now allowed to create a profile,
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > including some
>> > > > > > > > > > details about it, like a description, its working
>> fields, its
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > size,
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > etc...
>> > > > > > > > > > . Moreover, users can be linked to the organizations
>> they
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > belong to,
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > and
>> > > > > > > > > > projects can be linked to the organizations developing
>> them.
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > For both
>> > > > > > > > >
>> > > > > > > > > these
>> > > > > > > > > > kinds of relationships, we implemented a two-way
>> mechanism:
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > the user
>> > > > > > > > > > requests to be registered as a member of the
>> organization and
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > the
>> > > > > > > > > > organization has to confirm it, or vice-versa.
>> Similarly, an
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > organization
>> > > > > > > > > > sends a request to be listed as the developer of a
>> project,
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > and the
>> > > > > > > > > > administrator of the project has to accept it, or
>> vice-versa.
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > When a
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > user
>> > > > > > > > > > leaves an organization, he can set this on the forge,
>> and the
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > enrollment
>> > > > > > > > > in
>> > > > > > > > > > this organization will be shown as a past membership.
>> The same
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > applies
>> > > > > > > > >
>> > > > > > > > > for
>> > > > > > > > > > project collaborations: an organization can freely set a
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > collaboration
>> > > > > > > > > > within a project as completed, because the organization
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > doesn't want
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > to
>> > > > > > > > > > continue working on the project, and it will be shown
>> as a past
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > involvement.
>> > > > > > > > > > We believe this features could be very useful on a
>> forge which
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > is
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > used by
>> > > > > > > > > > more than one organization, because it allows to have a
>> better
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > awareness
>> > > > > > > > > of
>> > > > > > > > > > the community, knowing how users working on a project
>> are
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > organized in
>> > > > > > > > >
>> > > > > > > > > the
>> > > > > > > > > > real life. It can also increase trust for those projects
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > developed by
>> > > > > > > > > > well-known organizations.
>> > > > > > > > > >
>> > > > > > > > > > The second feature we developed is related to users, and
>> > > > consits of a
>> > > > > > > > set
>> > > > > > > > > > of metrics gathered from their activity.
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > This is a really interesting thing for me!
>> > > > > > > > >
>> > > > > > > > > > These metrics include the number
>> > > > > > > > > > of created or modified artifacts (also separated for
>> different
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > kinds
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > of
>> > > > > > > > > > artifacts), the number of assigned tickets, solved
>> tickets and
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > "revoked"
>> > > > > > > > > > tickets, namely tickets which were assigned to a user
>> but
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > whose owner
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > was
>> > > > > > > > > > later changed. Moreover, the number of commits is
>> collected,
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > together
>> > > > > > > > >
>> > > > > > > > > with
>> > > > > > > > > > the total number of added or modified lines of code by
>> the
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > user. For a
>> > > > > > > > > > certain user, all these metrics are shown on a page on
>> the
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > form, as a
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > total
>> > > > > > > > > > value since the user's registration, as well as an
>> average
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > per-month
>> > > > > > > > >
>> > > > > > > > > value.
>> > > > > > > > > > The metrics are also calculated considering the last 30
>> days
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > only, in
>> > > > > > > > >
>> > > > > > > > > order
>> > > > > > > > > > to allow to check whether the user is still active on
>> the
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > forge or
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > not,
>> > > > > > > > > and
>> > > > > > > > > > if he is increasing his efforts on the forge or not.
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > Is this code already available?
>> > > > > > > > >
>> > > > > > > > > In Bitergia our main focus is analyzing software projects
>> using
>> > > > metrics
>> > > > > > > > > and we are integrating some of our tools in Allura. We
>> are using
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > a
>> > > > > > > > > different approach from you, getting the metrics from a
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > consolidated
>> > > > > > > > > database that gathers the data from Allura, but at the
>> end, the
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > metrics
>> > > > > > > > > are really similar.
>> > > > > > > > >
>> > > > > > > > > We are working in different kind of visualization also,
>> so we
>> > > > can share
>> > > > > > > > > also here experiences.
>> > > > > > > > >
>> > > > > > > > > > Moreover, it is also possible to see these values for a
>> single
>> > > > > > > > category
>> > > > > > > > > > only, namely considering all the data regarding projects
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > tagged as
>> > > > > > > > > > belonging to that category. A graph showing the number
>> of
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > joined
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > projects
>> > > > > > > > > > by the user for each category is also shown, to
>> highlight the
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > kind of
>> > > > > > > > > > applications the user is focused on.
>> > > > > > > > > > Finally, the previously listed statistics are also
>> calculated
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > for
>> > > > > > > > > > organizations, by considering the activity of the users
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > enrolled in
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > the
>> > > > > > > > > > organization itself. Particularly, since each user can
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > possibly work
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > for
>> > > > > > > > > > more than one organization on the forge, as well as
>> working as
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > an
>> > > > > > > > > > individual programmer, organizations' statistics are
>> calculated
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > considering
>> > > > > > > > > > only those activities performed by its members on
>> projects to
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > which
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > the
>> > > > > > > > > > organizatione is explicitely involved.
>> > > > > > > > > > We think these features are useful to allow users to
>> have a
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > deeper
>> > > > > > > > > > awareness of someone else's experience and interests,
>> and this
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > could
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > also
>> > > > > > > > > > help in identifying partners for a certain project.
>> > > > > > > > > >
>> > > > > > > > > > These features are implemented as external features and
>> can be
>> > > > easily
>> > > > > > > > > > enabled or disabled by setting boolean parameters in
>> the .ini
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > file.
>> > > > > > > > > > Therefore, it is possible to enable organizations only,
>> without
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > including
>> > > > > > > > > > the statistics features, or including statistics for
>> users
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > only, and
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > so
>> > > > > > > > > on.
>> > > > > > > > > > Of course, it is not possible to enable organization
>> statistics
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > without
>> > > > > > > > > > enabling the concept of organization on the forge.
>> > > > > > > > > >
>> > > > > > > > > > We would like to know what you think about these
>> features, and
>> > > > we
>> > > > > > > > would
>> > > > > > > > > > like to know how we can provide you our code to get a
>> feedback
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > from
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > you
>> > > > > > > > > > and, eventually, to discuss improvements and changes on
>> it.
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > I think it is a really good use case por the code
>> contributors
>> > > > policy
>> > > > > > > > > proposed in the mailing list.
>> > > > > > > > >
>> > > > > > > > > > Stefano is now
>> > > > > > > > > > allowed to write on the repositoy, but since I am not
>> allowed
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > to do
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > so,
>> > > > > > > > > and
>> > > > > > > > > > since these features should obviously be discussed
>> before being
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > included
>> > > > > > > > > on
>> > > > > > > > > > the project, I don't know if working there, even on a
>> new
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > branch, is
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > the
>> > > > > > > > > > best solution.
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > I think so. Create a new experimental branch and upload
>> the code
>> > > > to
>> > > > > > > > > Allura so for others developers like me, it is easy to
>> start
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > playing
>> > > > > > > > > with it.
>> > > > > > > > >
>> > > > > > > > > Cheers
>> > > > > > > > >
>> > > > > > > > > > Also, let us know if you prefer to check the two
>> features
>> > > > > > > > > > separately or not. Probably, it would be easier to do it
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > incrementally,
>> > > > > > > > > > considering one of them at a time.
>> > > > > > > > > >
>> > > > > > > > > > Regards,
>> > > > > > > > > >
>> > > > > > > > > > Simone Gatti and Stefano Invernizzi
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > --
>> > > > > > > > > |\_____/| Alvaro del Castillo
>> > > > > > > > > [o] [o] acs@bitergia.com (mailto:acs@bitergia.com)
>> (mailto:acs@bitergia.com) - CTO,
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > Software Engineer
>> > > > > > > > > | V | http://www.bitergia.com
>> > > > > > > > > | |
>> > > > > > > > > -ooo-ooo-
>> > > > > > > > > |\_____/| Alvaro del Castillo
>> > > > > > > > > [o] [o] acs@bitergia.com (mailto:acs@bitergia.com)
>> (mailto:acs@bitergia.com) - CTO,
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > > Software Engineer
>> > > > > > > > > | V | http://www.bitergia.com
>> > > > > > > > > | |
>> > > > > > > > > -ooo-ooo-
>> > > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > > >
>> > >
>> > >
>> > >
>> > >
>> >
>> >
>>
>>
>
Re: User stats and organizations
Posted by Stefano Invernizzi <st...@gmail.com>.
Hi,
Yes, you are right! I changed the name of the parameter in the
configuration file, but I forgot to do the same in the test.ini file,
therefore all our tests resulted in errors or failures. I changed the
parameter in that file and now it looks like everything is ok. I'm sorry
about that.
Stefano
2013/2/1 Tim Van Steenburgh <tv...@gmail.com>
> Hey guys,
>
> I've started to look at this again. Getting several errors and failures
> running `nosetests` in ForgeUserStats. Can you look into that?
>
> Tim
>
>
> On Wednesday, January 30, 2013 at 2:17 PM, Tim Van Steenburgh wrote:
>
> > Thanks guys! I'm in the middle of another code review at the moment, but
> I'll take a look soon.
> >
> > Tim
> >
> > On Wednesday, January 30, 2013 at 12:36 PM, Stefano Invernizzi wrote:
> >
> > > Dear Tim,
> > > After fixing the issues you reported in your first review, we also
> fixed
> > > other things today and we committed them to the repository.
> > > We hope this improves our code. We also implemented the loop to
> register
> > > additional listeners, as I had explained in the discussion of the
> ticket a
> > > few days ago. Particularly, we forced the parameter in the
> configuration
> > > file to be the equal to the entry point name, followed by ".enable", so
> > > that the whole mechanism can be easily extended.
> > > Let us know what you think about this additional commits and if there
> other
> > > things to be improved. Thank you again for your review!
> > >
> > > Stefano & Simone
> > >
> > >
> > > 2013/1/18 Tim Van Steenburgh <tvansteenburgh@gmail.com (mailto:
> tvansteenburgh@gmail.com)>
> > >
> > > > Stefano & Simone,
> > > >
> > > > I've posted a first review of the User stats code on
> > > > https://sourceforge.net/p/allura/tickets/5453/.
> > > >
> > > > Tim Van Steenburgh
> > > >
> > > >
> > > >
> > > > On Wednesday, January 9, 2013 at 11:30 PM, Tim Van Steenburgh wrote:
> > > >
> > > > > Hi Stefano & Simone,
> > > > >
> > > > > Sorry for the delay, a lot of us were on extended vacation for the
> > > > Christmas holiday. I've begun looking at your branch and intend to
> provide
> > > > some feedback in the near future. Thanks for your contribution to
> Allura!
> > > > >
> > > > > Tim Van Steenburgh
> > > > >
> > > > >
> > > > > On Wednesday, January 9, 2013 at 4:14 AM, Stefano Invernizzi wrote:
> > > > >
> > > > > > Dear all,
> > > > > >
> > > > > > We still didn't get any feedback about the uploaded code.
> Please, let
> > > > us
> > > > > > know what you think about it and if there's something we can
> improve.
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Simone & Stefano
> > > > > >
> > > > > >
> > > > > > 2012/12/13 Stefano Invernizzi <stefano.invernizzi88@gmail.com(mailto:
> stefano.invernizzi88@gmail.com) (mailto:
> > > > stefano.invernizzi88@gmail.com (mailto:
> stefano.invernizzi88@gmail.com))>
> > > > > >
> > > > > > > Dear all,
> > > > > > > Since yesterday the code is available on the repository. As
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > > suggested in
> > > > > > > the proposed code contributors policy, I created a new branch
> named
> > > > > > > si/5453. Feel free to comment our work, and send feedbacks or
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > suggestions
> > > > > > > about possible improvements.
> > > > > > >
> > > > > > > Stefano & Simone
> > > > > > >
> > > > > > >
> > > > > > > 2012/12/11 Simone Gatti <simone.gatti88@gmail.com (mailto:
> simone.gatti88@gmail.com) (mailto:
> > > > simone.gatti88@gmail.com (mailto:simone.gatti88@gmail.com))>
> > > > > > >
> > > > > > > > Dear all,
> > > > > > > >
> > > > > > > > thank you for your feedback!!
> > > > > > > > First of all, in the next hours we'll create a branch with
> the
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > extension
> > > > > > > > of
> > > > > > > > UserStats, so that you can see our code to discuss it and its
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > possible
> > > > > > > > improvements. After that we'll upload the extensions of the
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > Organization
> > > > > > > > and OrganizationStats.
> > > > > > > > About the possibility to define an organization based on a
> shared
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > topic of
> > > > > > > > interest, we have not considered it. We assumed that the
> kind of
> > > > > > > > organization could be: "for-profit business", "foundation or
> other
> > > > > > > > non-profit organization" or "research and/or education
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > institution", like
> > > > > > > > the organizations in the real world. We don't know if the
> concept
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > is the
> > > > > > > > same, in that case we can easily add a new type of
> organization.
> > > > > > > > (e.g."group of interest").
> > > > > > > > As for Rich's proposal it's a great idea! We have considered
> it
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > but we
> > > > > > > > later decided to focus on other aspects in our thesis.
> Anyway it's
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > the
> > > > > > > > best
> > > > > > > > way to use the additional data included in the profile.
> > > > > > > > I don't have commit access on the repository to upload my
> code.
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > Since we
> > > > > > > > developed it together, Stefano will commit it.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > >
> > > > > > > > Simone.
> > > > > > > >
> > > > > > > >
> > > > > > > > 2012/12/10 Alvaro del Castillo <acs@bitergia.com (mailto:
> acs@bitergia.com) (mailto:
> > > > acs@bitergia.com (mailto:acs@bitergia.com))>
> > > > > > > >
> > > > > > > > > Dear Simone,
> > > > > > > > >
> > > > > > > > > First of all, I am sorry about the delayed response.
> > > > > > > > >
> > > > > > > > > El jue, 29-11-2012 a las 19:06 +0100, Simone Gatti
> escribió:
> > > > > > > > > > Dear all,
> > > > > > > > > >
> > > > > > > > > > During the last weeks, while discussing our work on
> including
> > > > new
> > > > > > > > details
> > > > > > > > > > in users' profiles on the forge, I and Stefano
> Invernizzi also
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > continued
> > > > > > > > > > working on the other features we introduced in one of
> our first
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > messages
> > > > > > > > > on
> > > > > > > > > > the mailing list, back in July.
> > > > > > > > > > Now we have completed the implementation of these tools,
> and
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > we would
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > like
> > > > > > > > > > to get feedbacks from you in order to check if it's
> possible to
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > include
> > > > > > > > > > them on the Allura platform.
> > > > > > > > > >
> > > > > > > > > > The additional features we implemented consist of two
> main
> > > > parts.
> > > > > > > > First
> > > > > > > > > of
> > > > > > > > > > all, we included the concept of organization, namely
> companies,
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > foundations
> > > > > > > > > > or other non-profit organizations and research and
> education
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > institutions.
> > > > > > > > > > Each organization is now allowed to create a profile,
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > including some
> > > > > > > > > > details about it, like a description, its working
> fields, its
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > size,
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > etc...
> > > > > > > > > > . Moreover, users can be linked to the organizations they
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > belong to,
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > and
> > > > > > > > > > projects can be linked to the organizations developing
> them.
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > For both
> > > > > > > > >
> > > > > > > > > these
> > > > > > > > > > kinds of relationships, we implemented a two-way
> mechanism:
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > the user
> > > > > > > > > > requests to be registered as a member of the
> organization and
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > the
> > > > > > > > > > organization has to confirm it, or vice-versa.
> Similarly, an
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > organization
> > > > > > > > > > sends a request to be listed as the developer of a
> project,
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > and the
> > > > > > > > > > administrator of the project has to accept it, or
> vice-versa.
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > When a
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > user
> > > > > > > > > > leaves an organization, he can set this on the forge,
> and the
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > enrollment
> > > > > > > > > in
> > > > > > > > > > this organization will be shown as a past membership.
> The same
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > applies
> > > > > > > > >
> > > > > > > > > for
> > > > > > > > > > project collaborations: an organization can freely set a
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > collaboration
> > > > > > > > > > within a project as completed, because the organization
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > doesn't want
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > to
> > > > > > > > > > continue working on the project, and it will be shown as
> a past
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > involvement.
> > > > > > > > > > We believe this features could be very useful on a forge
> which
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > is
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > used by
> > > > > > > > > > more than one organization, because it allows to have a
> better
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > awareness
> > > > > > > > > of
> > > > > > > > > > the community, knowing how users working on a project are
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > organized in
> > > > > > > > >
> > > > > > > > > the
> > > > > > > > > > real life. It can also increase trust for those projects
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > developed by
> > > > > > > > > > well-known organizations.
> > > > > > > > > >
> > > > > > > > > > The second feature we developed is related to users, and
> > > > consits of a
> > > > > > > > set
> > > > > > > > > > of metrics gathered from their activity.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > This is a really interesting thing for me!
> > > > > > > > >
> > > > > > > > > > These metrics include the number
> > > > > > > > > > of created or modified artifacts (also separated for
> different
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > kinds
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > of
> > > > > > > > > > artifacts), the number of assigned tickets, solved
> tickets and
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > "revoked"
> > > > > > > > > > tickets, namely tickets which were assigned to a user but
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > whose owner
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > was
> > > > > > > > > > later changed. Moreover, the number of commits is
> collected,
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > together
> > > > > > > > >
> > > > > > > > > with
> > > > > > > > > > the total number of added or modified lines of code by
> the
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > user. For a
> > > > > > > > > > certain user, all these metrics are shown on a page on
> the
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > form, as a
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > total
> > > > > > > > > > value since the user's registration, as well as an
> average
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > per-month
> > > > > > > > >
> > > > > > > > > value.
> > > > > > > > > > The metrics are also calculated considering the last 30
> days
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > only, in
> > > > > > > > >
> > > > > > > > > order
> > > > > > > > > > to allow to check whether the user is still active on the
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > forge or
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > not,
> > > > > > > > > and
> > > > > > > > > > if he is increasing his efforts on the forge or not.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Is this code already available?
> > > > > > > > >
> > > > > > > > > In Bitergia our main focus is analyzing software projects
> using
> > > > metrics
> > > > > > > > > and we are integrating some of our tools in Allura. We are
> using
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > a
> > > > > > > > > different approach from you, getting the metrics from a
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > consolidated
> > > > > > > > > database that gathers the data from Allura, but at the
> end, the
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > metrics
> > > > > > > > > are really similar.
> > > > > > > > >
> > > > > > > > > We are working in different kind of visualization also, so
> we
> > > > can share
> > > > > > > > > also here experiences.
> > > > > > > > >
> > > > > > > > > > Moreover, it is also possible to see these values for a
> single
> > > > > > > > category
> > > > > > > > > > only, namely considering all the data regarding projects
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > tagged as
> > > > > > > > > > belonging to that category. A graph showing the number of
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > joined
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > projects
> > > > > > > > > > by the user for each category is also shown, to
> highlight the
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > kind of
> > > > > > > > > > applications the user is focused on.
> > > > > > > > > > Finally, the previously listed statistics are also
> calculated
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > for
> > > > > > > > > > organizations, by considering the activity of the users
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > enrolled in
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > the
> > > > > > > > > > organization itself. Particularly, since each user can
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > possibly work
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > for
> > > > > > > > > > more than one organization on the forge, as well as
> working as
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > an
> > > > > > > > > > individual programmer, organizations' statistics are
> calculated
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > considering
> > > > > > > > > > only those activities performed by its members on
> projects to
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > which
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > the
> > > > > > > > > > organizatione is explicitely involved.
> > > > > > > > > > We think these features are useful to allow users to
> have a
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > deeper
> > > > > > > > > > awareness of someone else's experience and interests,
> and this
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > could
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > also
> > > > > > > > > > help in identifying partners for a certain project.
> > > > > > > > > >
> > > > > > > > > > These features are implemented as external features and
> can be
> > > > easily
> > > > > > > > > > enabled or disabled by setting boolean parameters in the
> .ini
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > file.
> > > > > > > > > > Therefore, it is possible to enable organizations only,
> without
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > including
> > > > > > > > > > the statistics features, or including statistics for
> users
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > only, and
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > so
> > > > > > > > > on.
> > > > > > > > > > Of course, it is not possible to enable organization
> statistics
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > without
> > > > > > > > > > enabling the concept of organization on the forge.
> > > > > > > > > >
> > > > > > > > > > We would like to know what you think about these
> features, and
> > > > we
> > > > > > > > would
> > > > > > > > > > like to know how we can provide you our code to get a
> feedback
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > from
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > you
> > > > > > > > > > and, eventually, to discuss improvements and changes on
> it.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I think it is a really good use case por the code
> contributors
> > > > policy
> > > > > > > > > proposed in the mailing list.
> > > > > > > > >
> > > > > > > > > > Stefano is now
> > > > > > > > > > allowed to write on the repositoy, but since I am not
> allowed
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > to do
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > so,
> > > > > > > > > and
> > > > > > > > > > since these features should obviously be discussed
> before being
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > included
> > > > > > > > > on
> > > > > > > > > > the project, I don't know if working there, even on a new
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > branch, is
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > the
> > > > > > > > > > best solution.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I think so. Create a new experimental branch and upload
> the code
> > > > to
> > > > > > > > > Allura so for others developers like me, it is easy to
> start
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > playing
> > > > > > > > > with it.
> > > > > > > > >
> > > > > > > > > Cheers
> > > > > > > > >
> > > > > > > > > > Also, let us know if you prefer to check the two features
> > > > > > > > > > separately or not. Probably, it would be easier to do it
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > incrementally,
> > > > > > > > > > considering one of them at a time.
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > >
> > > > > > > > > > Simone Gatti and Stefano Invernizzi
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > |\_____/| Alvaro del Castillo
> > > > > > > > > [o] [o] acs@bitergia.com (mailto:acs@bitergia.com)
> (mailto:acs@bitergia.com) - CTO,
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > Software Engineer
> > > > > > > > > | V | http://www.bitergia.com
> > > > > > > > > | |
> > > > > > > > > -ooo-ooo-
> > > > > > > > > |\_____/| Alvaro del Castillo
> > > > > > > > > [o] [o] acs@bitergia.com (mailto:acs@bitergia.com)
> (mailto:acs@bitergia.com) - CTO,
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > Software Engineer
> > > > > > > > > | V | http://www.bitergia.com
> > > > > > > > > | |
> > > > > > > > > -ooo-ooo-
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
>
>