> Is the intention to document the architecture? To host discussion of the > architecture? Or to collect tickets likely to impact the architecture? I > think the first is valuable, the second much less valuable, and the third > destined to be stale immediately. >
Originally the page was setup as a jumping off point for current architecture discussions that are happening in Bugzilla to make it more visible to contributors and other members of the team. I find that these larger bugs tend to get buried along with all of the other bugs we have filed. Now that I think of it, it might be better just replace that with a link to a Bugzilla query that looks for a flag so it's always up-to-date and use the wiki for more in-stone architectural discussions as you mentioned in the first part of your question. On Thu, Oct 29, 2015 at 6:58 PM, Mark Finkle <[email protected]> wrote: > Nick, > > I bet your Accounts Integration is worth a standalone page. Steph (or > others) can find a way to work it into the Planning & Arch page. Maybe that > page needs a Planning section (exists) and an Arch section (nothing there > yet). > > On Thu, Oct 29, 2015 at 4:40 PM, Nicholas Alexander < > [email protected]> wrote: > >> Hi iOS team, >> >> On Thu, Oct 29, 2015 at 11:40 AM, Steph Leroux <[email protected]> >> wrote: >> >>> Hello mobile-devers, >>> >>> As discussed during our iOS team meeting, I've setup a wiki page in our >>> Github repo that links out to some of the larger feature and architecture >>> bugs we have planned here: >>> https://github.com/mozilla/firefox-ios/wiki/Planning-&-Architecture-Documentation. >>> The motivation behind this page is to have a single place where we can >>> refer other members of the team and contributors to discussions around >>> architecture/feature changes - the idea being that discussions and >>> documentation are part of the Bugzilla bugs with the wiki page serving as >>> an accessible access point to higher level topics. >>> >> >> I just went to that page, thinking I would write a few words about how >> the existing Accounts integration works, and how it impacts the rest of the >> App. The page doesn't set any example for that, so I ask: >> >> Is the intention to document the architecture? To host discussion of the >> architecture? Or to collect tickets likely to impact the architecture? I >> think the first is valuable, the second much less valuable, and the third >> destined to be stale immediately. >> >> I've probably missed some things in the list that should be added so feel >>> free to add any relevant links or topics to the wiki page. I'm open to >>> moving this over to MozWiki or somewhere else if it makes more sense - just >>> the first iteration. Thanks! >>> >> >> I think the final resting place must be informed by the intention, so I >> won't comment on the initial choice of location. >> >> Yours, >> Nick >> >> _______________________________________________ >> mobile-firefox-dev mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/mobile-firefox-dev >> >> >
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
