[p2pu-dev] metrics script - github?

[zuzel.vp]

Sounds good. -- Then you can from time to time download the latest
lernanta code and run the migrations on you copy of the db so you can
update the scripts (and update the setup of Degress-of-Freedom in
production on release days).

-- 
Thanks,
    Zuzel

On Tue, Jun 21, 2011 at 7:38 PM, Jessy Kate Schingler
<jessy at jessykate.com> wrote:
> yeah-- but just to be clear, this isn't meant to be *part of* lernanta--
> it's just a script to give us a sense of metrics regarding participation.
>  so for example, showing some tables, graphs, stats, etc.
> i don't see that as conceptually part of lernanta, unless you think we
> could/should integrate it into admin somehow? IMHO this is more effort than
> it's worth, especially right now as we figure out what we want to include,
> but that could be because i'd have to learn how to do that :). but i would
> imagine (eventually!) something more like munin's output than a typical
> django admin interface, eg:
> http://oierud.name/bliki/munin-mysql.png
> anyhoo, in the meantime i've set up a repo here:
> https://github.com/p2pu/Degress-of-Freedom
> we can always merge if that's the direction we want to go!
> (as a side note-- is it possible to create a repo within an organization
> without first creating one within your personal account and then forking it?
> seems a little silly but i couldnt find another way to do it).
>
>
> Jessy
> --
> http://jessykate.com
>
>
> On Mon, Jun 20, 2011 at 7:51 PM, zuzel.vp <zuzel.vp at gmail.com> wrote:
>>
>> If it will have its own front end then it makes sense to have another
>> repo. Any reason why you are not using the lernanta as frontend?
>>
>> --
>> Thanks,
>>    Zuzel
>>
>> On Mon, Jun 20, 2011 at 12:21 PM, Jessy Kate Schingler
>> <jessy at jessykate.com> wrote:
>> > they are definitely wholly dependent on the DB schema, but other than
>> > that
>> > not really related in terms of development. also it will end up having
>> > it's
>> > own front end as well-- something simple, but seems like it would be
>> > clutter
>> > in the lernanta repo. i dunno, i think it probably makes more sense to
>> > create a separate repo-- but am easy if you feel strongly!
>> >
>> > Jessy
>> > --
>> > http://jessykate.com
>> >
>> >
>> > On Mon, Jun 20, 2011 at 12:14 PM, zuzel.vp <zuzel.vp at gmail.com> wrote:
>> >>
>> >> If they are scripts (quite related to lernanta) maybe you could submit
>> >> them to the lernanta repo (they could be in their own folder). If we
>> >> update the db schema in parts that those scripts are using we could
>> >> update them at the same time.
>> >>
>> >> --
>> >> Thanks,
>> >>    Zuzel
>> >>
>> >> On Mon, Jun 20, 2011 at 12:10 PM, Jessy Kate Schingler
>> >> <jessy at jessykate.com> wrote:
>> >> > awesome, i'll start a repo.
>> >> >
>> >> > Jessy
>> >> > --
>> >> > http://jessykate.com
>> >> >
>> >> >
>> >> > On Sun, Jun 19, 2011 at 11:53 PM, zuzel.vp <zuzel.vp at gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> Yes, the structure of the database is public. It makes sense to
>> >> >> store
>> >> >> and maintain the script on github.
>> >> >>
>> >> >>
>> >> >> On Sunday, June 19, 2011, Jessy Kate Schingler <jessy at jessykate.com>
>> >> >> wrote:
>> >> >> > thoughts about putting the metrics script on github?
>> >> >> > (for reminder/information, the metrics script will give us a set
>> >> >> > of
>> >> >> > stats on participation and engagement across different strata--
>> >> >> > basic
>> >> >> > stuff
>> >> >> > like users per course and school, etc. and evolving over time. our
>> >> >> > etherpad
>> >> >> > on desired metrics is here: http://pad.p2pu.org/metrics, and the
>> >> >> > queries in
>> >> >> > bold are what the initial script will focus on)
>> >> >> >
>> >> >> > it is essentially a bunch of raw sql queries against the DB. it
>> >> >> > doesn't
>> >> >> > involve any personal information, and only retrieves counts
>> >> >> > of aggregates.
>> >> >> > however, i know the DB is sensitive, and there is arguably
>> >> >> > security
>> >> >> > through
>> >> >> > obscurity in terms of DB structure. on the other hand, i don;t
>> >> >> > think
>> >> >> > it
>> >> >> > reveals anything sensitive, and anyone familiar with django would
>> >> >> > know what
>> >> >> > our DB looks like by reading the lernanta code, and having it on
>> >> >> > github will
>> >> >> > allow others to contribute.
>> >> >> >
>> >> >> > input?
>> >> >> > Jessy--http://jessykate.com
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> _______________________________________________
>> >> >> p2pu-dev mailing list
>> >> >> p2pu-dev at lists.p2pu.org
>> >> >> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > p2pu-dev mailing list
>> >> > p2pu-dev at lists.p2pu.org
>> >> > http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>> >> >
>> >> >
>> >> _______________________________________________
>> >> p2pu-dev mailing list
>> >> p2pu-dev at lists.p2pu.org
>> >> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>> >
>> >
>> > _______________________________________________
>> > p2pu-dev mailing list
>> > p2pu-dev at lists.p2pu.org
>> > http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>> >
>> >
>> _______________________________________________
>> p2pu-dev mailing list
>> p2pu-dev at lists.p2pu.org
>> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>
>
> _______________________________________________
> p2pu-dev mailing list
> p2pu-dev at lists.p2pu.org
> http://lists.p2pu.org/mailman/listinfo/p2pu-dev
>
>