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 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
James Tauber
@jtauber
it occurs to me that locally you could have, say, PPA, with two remotes set up: one the master of the PPA repo and one the PPA-branch of the pinax-project repo. That’s how you could basically keep them in sync
Jacob Wegner
@jacobwegner
Patrick Altman
@paltman
@jtauber are you going to comment on the gist or should one of us?
Thans jake!
James Tauber
@jtauber
i’ll respond
James Tauber
@jtauber
@paltman we should consider donating kaleo soon
Patrick Altman
@paltman
Yup
In conjunction with private beta project
James Tauber
@jtauber
yep
Patrick Altman
@paltman
Never mind
James Tauber
@jtauber
which can get waitinglist some love too
nevermind?
Patrick Altman
@paltman
That's waiting list
James Tauber
@jtauber
true
Patrick Altman
@paltman
Kaleo is still