Re: [Ubuntu-phone] Feedback and Bug App

2014-12-17 Thread Stephen P. Villano

On 12/17/14 12:17 AM, Robert Schroll wrote:
> Let me play devil's advocate here.  This isn't because I think it's a
> bad idea (I think we need more feedback, in general), but because I
> think this proposal needs a bit of tightening to give us a worthwhile
> product.
>
> Firstly, I don't see anything here that requires an app.  All of this
> could be done on a website.  Once you have a website, you can make a
> webapp for Ubuntu very easily.  If there's a reason this has to be an
> app, that should be clarified.
>
> On Tue, Dec 16, 2014 at 4:30 PM, Alexander Langanke
>  wrote:
>> This would be a Blog updated (for example) once or twice a month
>> announcing the most important changes that have landed so far in
>> order to draw attention to them and encourage feedback on these
>> topics. Of course this could also be used to just keep the community
>> informed in general. I would love to see the different teams updating
>> here regularly. For example I have read about an upcoming Blog for
>> Unity that is to be created in the near future, would love to get
>> updates on Unity Next, the Phone, Ubuntu TV etc. without checking
>> different sites.
>
> I'm confused about what exactly would appear on this blog.  If it's
> only updated once every two weeks, it's not going to be go-to reading
> for anyone.  I'd wait for these posts to be syndicated on Planet
> Ubuntu.  If it's supposed to be aggregating a bunch of blogs, isn't
> that what Planet Ubuntu is already doing?
>
>> 2. Missions
>> This is a place where Core Developers and perhaps any other developer
>> (not sure on that yet) can post small things they specifically want
>> users to check out, test and give feedback on.
>> Here we are looking for Feedback in terms of "quality" and not
>> "quantity".
>> See Mockup Image.
>>
>> 3. Polls
>> A place where we can gather feedback in a quantifiable sense. How
>> many people like the new iconsets? How many people think Unity Next
>> should have Windows on the Desktop etc. You get the picture..
>> See Mockup Image.
>
> The Ubuntu App Developers community on Google+ is already used for
> this purpose.  What does this offer that Google+ does not?
>
> I'm also skeptical of the usefulness of polls with self-selected
> respondents.  They tend to tell you only what people who feel strongly
> about an issue think, which may not be the same as what most people
> think.
>
>> 4. General Feedback
>> Here a User can select different official Ubuntu Flavors, Topics and
>> Packages/Projects to give feedback on or send in an Idea without the
>> need of a "Mission" or "Poll".
>
> Why would this work any better than the now-defunct Ubuntu Brainstorm
> site?
>
> Where would this information go?  As a developer, I rather have bugs
> and feature requests on my issue tracker, rather than on some external
> site.
>
> Thanks,
> Robert
>
>
At the risk of sounding ill informed, I'll also ask, does Ubuntu-phone
not have a version of "full sized" Ubuntu error reporting?
When my desktop and server Ubuntu computers experience a crashed
program, I typically get a dialog box asking if I want to report the
issue to Ubuntu. On most of my machines, I do, on isolated or sensitive
machines, I cannot.
So, if that error reporting is already present, wouldn't this largely be
re-inventing a wheel?

As for bug reporting, I'd think that waiting for a consolidated site is
established and web-app to the site. Let the big iron do the heavy
lifting and use the phone more like a thin client.

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Questions about code reviews and static analysis tools for TU Delft research

2014-12-17 Thread Radjino Bholanath
Hi,

I'm doing research on code reviews and static analysis tools at the SERG group 
(http://swerl.tudelft.nl/bin/view/Main/WebHome) of the Delft University of 
Technology. Currently, we want to give an overview of the usage of code review 
and static analysis tools in open source projects. Therefore, I would be very 
happy to know a little bit more about how code reviews are used in Ubuntu and 
if (and maybe how) static analysis tools are used. I have a couple of questions 
for anyone willing to answer:

1. Do all developers (contributors and core developers) have to submit a code 
review for every change? I’m asking because many projects only review changes 
made by contributors.
2. Which code review tools are used?
3. Are static analyzers used? If they are used:
a. Is passing the checks of the static analyzers necessary for a change to be 
accepted?
b. Which static analyzers are used?

Thanks,
Radjino
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss


Re: [Ubuntu-phone] Feedback and Bug App

2014-12-17 Thread Sam Bull
On mer, 2014-12-17 at 00:17 -0500, Robert Schroll wrote:
> Firstly, I don't see anything here that requires an app.  All of this 
> could be done on a website.  Once you have a website, you can make a 
> webapp for Ubuntu very easily.

I would agree with that.

What I would like to see is reporting issues to the developers made
trivial. At the moment, if I want to report a bug, I wait till I get
home and then access Launchpad from my laptop to file a bug (sometimes
days or weeks later, if I remember at all).

There are two issues I can initially think of that could be solved by an
app.

Firstly, I should be able to immediately report a bug without having to
navigate to Launchpad and have to work out my login details.
I believe you login to Launchpad with an Ubuntu One account, therefore
this can be easily solved with a webapp using UOA and skipping the login
screen.

Secondly, there are a large number of different projects/components and
most users have no idea what component to register a bug against.

There are various approaches that might help solve this. Firstly, having
a list of projects which are associated with the phone, and ensuring
every project has a one line description that clearly explains to an end
user what the component does would be a good start.

The app could then also be augmented to allow selecting an app on the
phone, or clicking a component on the screen to suggest possible
projects that may be responsible.

Another idea is some kind of natural language/machine learning algorithm
which parses the bug report and suggests which components may be
responsible for the issue.


signature.asc
Description: This is a digitally signed message part
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss