0a. Remember this is just about the minimal I could do to get things going.
Plenty more feature could be implemented to make it better. They'll come
slowly based on demand (aka: we really need something to make our lives
more enjoyable). <smile/>
0b. Thank you very much for the feedback.
1. Yeah, I dislike this too but seem to have forgotten to file a bug on it.
Issue #30
2. I really only wanted to support one login mechanism to make it easy.
Originally, I was only going to support Twitter/Facebook or something like
that to make tinyBugs "socially aware" (random idea, not sure how it would
have worked for people that have no social accounts <smile/>). However, the
world seems to be resisting that and even places that support OpenID also
have a custom login system. Anyway, I'm mixed about additional login
mechanisms but I've opened issue #31 to track it.
3. I'm skeptical that people search much now. We do the search and tell
people when they opened a duplicate.<smile/> Anyway, I was hoping to do
the work to get the "real search engines" to search our bugs as the primary
way people find issues. However, I also got lucky that SQLite supports full
text search so I slipped in the search functionality because Bob asked for
it too. Anyway, an edit box is easy and it could be made more useful than
telling people to type in the address bar. Issue #32
4. Yeah, the front page hasn't got a lot of attention. In fact, it was the
last thing I did just before I posted the site. Last thing I did was to
make the rhs halfway useful. It's definitely not perfect, for example, the
tabs thing doesn't work correctly yet (Issue #28). Anyway, there is more UI
work to do on the search page. Issue #33.
5. Definitely need a subscription/notification mechanism. I like ATOM (not
RSS <smile/>) but wasn't sure people used it anymore. I was thinking of
using email as subscription because everyone uses that. I really only want
to support *one* mechanism and since I want to make sure that tinyBugs
appropriately pesters the people bugs are created by and assigned to, it
seems like email is the only real way to go. I could just use email to
poke the created by/assigned to and say that to subscribe otherwise you use
ATOM (that might work out well). Thoughts?
Overall, tinyBugs is designed to be tiny (aka: simple, compact, light, aka:
not big, not heavy, not too much stuff all over the place). But I also want
it to be very functional (aka: useful, helpful, does what needs to be done,
aka: not too small, not overly simple). So, ultimately I hope to have a
single solution for any particular way of doing things (to avoid lots of
configuration). I'm open to opinions what the best way solution is for any
single problem but in tinyBugs ideally only one solution is implemented.
Finally, I want to point out the use of issue #'s above. My hope is that
by making the issue tracker easier to use, we'll use it more to track what
we're doing to the WiX toolset. The ultimate goal being that it will be
clearer what people are working on (bugs and features) and how far we have
to progress for any given release. I'd love to get to a point where we are
using Issue #'s (from http://wixtoolset.org/) in our emails here regularly.
<smile/>
On Thu, Aug 15, 2013 at 12:03 AM, Neil Sleightholm <n...@x2systems.com>wrote:
> Few observations on the Issue Tracker:****
>
> **1. **The filter is case sensitive so type:Bug work but type:bug
> doesn’t****
>
> **2. **I would prefer to use an existing account rather than create
> something new, could you interface to OpenID?****
>
> **3. **I think an editbox for searching bugs would be better than
> having to use the URL; I suspect if this is not simple we will get
> duplicates as people won’t search.****
>
> **4. **I think there should be single click “Features” and “Bugs”
> shortcuts on the rhs.****
>
> **5. **Will it have an RSS feed?****
>
> ** **
>
> In general though I think it is better than SF.****
>
> ** **
>
> Neil****
>
> ** **
>
> *From:* Rob Mensching [mailto:r...@robmensching.com]
> *Sent:* 15 August 2013 00:06
> *To:* Windows Installer XML toolset developer mailing list
> *Subject:* [WiX-devs] WiX Toolset Issues and Triage****
>
> ** **
>
> Greetings all,****
>
> ** **
>
> *tl;dr*
>
> ** **
>
> **1. ***New Issue Tracker* - please experiment with new issue
> tracker sandbox: http://wixtoolset.org/bugout/****
>
> **a. **Send your blocking issues with the new issue tracker to me.**
> **
>
> **2. ***Regular WiX triage* – coming soon weekly or bi-weekly
> online meetings to discuss the state of WiX. ****
>
> **a. **Clear your calendar and make sure you can log in via
> Lync/Web Lync.****
>
> ** **
>
> ---****
>
> ** **
>
> *Update *
>
> ** **
>
> It’s been too long since I sent out status about what I’m working on. So
> here is an update.****
>
> ** **
>
> For the last few months, I’ve been heads down working on a bunch of “back
> office” improvements for the WiX toolset. The current “back office”
> infrastructure on SourceForge has been decaying for many years now. It’s
> been on Bob’s and my radar to migrate away from SF for a long time. I’m
> finally making time to do it (before SF falls apart completely <smile/>).*
> ***
>
> ** **
>
> One of the first projects you may have noticed was the documentation build
> was massively redone. One of the key goals of that project was to get the
> documentation updating on the WiX website again. I’m now in the final steps
> to throw the switch and redirect all traffic from the out of date
> http://wix.sf.net/ to http://wixtoolset.org/. I’m very excited to get
> that completed (probably over the weekend to minimize disruption).****
>
> ** **
>
> *Issue Tracker*
>
> ** **
>
> After the documentation build I turned my attention to our bugs. The “new”
> SourceForge issue tracker is a step down from the previous issue tracker
> that wasn’t all that great to begin with. So I looked at CodePlex and
> Github. The Codeplex tracker was not impressive but the Github tracker was
> pretty nice. However, both of them tie permissions to the issue tracker
> with permissions to the repository. That doesn’t work with the WiX toolset
> code flow (assignment agreements) so both were out.****
>
> ** **
>
> After looking at a bunch of different options (including YouTrack) that
> were all very complex systems, I considered creating a new issue tracker.
> There were a few web technologies I wanted to experiment with and an issue
> tracker was a great opportunity to do that. After a couple weeks, I’m quite
> happy with the new tracker functionality and expect it to really streamline
> our issue workflow.****
>
> ** **
>
> Please, take a little time to play in the current sandbox at
> http://wixtoolset.org/bugout/ ****
>
> ** **
>
> If all goes well and you guys provide enough feedback here, I hope to take
> this issue tracker live over the weekend.****
>
> ** **
>
> (source code at: http://github.com/robmen/tinybugs/ - note the code is at
> a bare minimum to support our needs in the WiX toolset, polishing will come
> with later releases).****
>
> ** **
>
> *Triage*
>
> ** **
>
> I would like to start hosting weekly or bi-weekly (every other week) WiX
> Triage online meetings. FireGiant (http://www.firegiant.com) has an O365
> account that I believe will allow me to host up to 200 people in an online
> meeting. I think that should support our needs.****
>
> ** **
>
> First order of business for the meeting will be to discuss our release
> schedule (WiX v3.8 anyone?). Second order of business will be to organize
> our backlog of bugs to match our desired release schedule. I expect the bug
> triage will take multiple sessions to complete.****
>
> ** **
>
> In preparation for that meeting I’ll be sending out meeting requests for
> later this week so you can practice connecting. Jump on the test meeting,
> verify that you say “Hi” to me (and hear me respond) then you’ll be ready
> for the real meeting. Additionally, please send me times that are **not**
> possible for you to meet. I’ll try hard to accommodate as many people as I
> can.****
>
> ** **
>
> I hope to have the first WiX Triage meeting sometime next week so get back
> to me quick. You wouldn’t want to miss the first meeting. <smile/>****
>
> ** **
>
> As always, feel free to send me questions/comments.****
>
> ** **
>
> virtually,****
>
> ** **
>
> Rob Mensching****
>
> Benevolent Dictator****
>
> WiX toolset****
>
> ** **
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-devs mailing list
> WiX-devs@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-devs
>
>
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
