Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Patrick Altman
@paltman
but it's close to the leave room
and then i have to go to the repo and click on the badge
James Tauber
@jtauber
it’s just hide from the list, not close
that’s kind of what I find confusing
Patrick Altman
@paltman
no i was clicking on the leave icon
James Tauber
@jtauber
oh
i find the hide thing annoying
Patrick Altman
@paltman
seems like such a silly thing to have so horribly wrong
James Tauber
@jtauber
I want a list of all my rooms, not a list of which ones I was most recently in :-)
and I don’t need to see all my orgs, most of whom don’t use gitter
Patrick Altman
@paltman
gitterHQ/gitter#581
Patrick Altman
@paltman
so i’d like to figure out if we can either 1) use mkdocs.org with RTD, or 2) host our own docs at urls like pinaxproject.com/pinax-teams/
@jtauber @brosner ^
either way i;d love to have our docs under their own theme
for branding
but of course that does communicate the whole “pinax app” instead of “just another django app”:
James Tauber
@jtauber
yeah, that seems a low priority compared to other things
Patrick Altman
@paltman
i do think it’s worth putting on the front matter of our docs and our README a blurb about what pinax is and that this app stands on its own (or with these dependancies)
i think @jtauber already mentioned this README idea
James Tauber
@jtauber
i’ve already got a PR in
Patrick Altman
@paltman
i only mention because as I have been doing a lot of foundation work on each app to update it to pinax-starter-app structure and/or doing donations from Eldarion to Pinax, part of that involves docs
and should i contineu doing Sphinx
granted i am not really writing comprehensive docs
James Tauber
@jtauber
Steven Wilcox thought the preamble was a great idea as he got confused by the pinax-* naming
Patrick Altman
@paltman
but rather just putting some stubs
yeah, it’s worth having a common preamble
James Tauber
@jtauber
i suggested one for pinax-blog
Patrick Altman
@paltman
cool
we can put it on all of them
James Tauber
@jtauber
if you think it’s okay, we can put it everywhere
I agree we need to mention dependencies, though, as some will, for example, assume DUA
and I think it’s much better to just say it assumes DUA than “it has to be a 100% Pinax project!” (which doesn’t make sense but people think that way)
Patrick Altman
@paltman
i was thinking for DUA we could make it optional
most dependency on DUA is for LoginRequiredMixin or decorator
and i think we can use DUA if it exists but roll back to contrib.admin if not
should the preamble include a brief bit about what Pinax is?
James Tauber
@jtauber
@paltman I’d love some system that automatically diffs starter projects that are based on one another so we remember to make upstream or downstream updates
ages ago I suggested whether actually making starter projects forks of each other (or at least branches) would enable us to use Git/Github for that but that seemed to complicate things
a better approach might just be something for modeling upstream relationship and providing easy diffing
but it seems tantalisingly like Git could be used for it :-)
Patrick Altman
@paltman
yeah
it might be worth experimenting with a pinax-project repo
put zero on master and then branch from there
account branch for PPA for example
then if PPA had versions it would breanch from account to things like account-1.2, account-1.2
i’d like to revisit this as branches
as that seems like that is really what they are
long lived branches
i guess the only difference with a typical branch is that they are never designed to merge upstream
but only get updates from upstream