[p2pu-dev] metrics script - github?

[zuzel.vp]

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
>
>