Re: Feedback on Package overview page - Distro tracker

2018-04-17 Thread Chirath R
>
> - I'd really love to see the version of the package in git; maybe it
>
  could be shown instead of the literal "Git"? And having the (then)
>   three columns with versions next to each other would be nice as
>   well.
> - Not sure if the "QA" label / link to vcswatch is that helpful, but
>   it doesn't really bother me either.
> - The various popups are really helpful IMO.
> - The "status" in the Git popup is nice; maybe it's possible to also
>   add the trailer line of the top changelog entry?
> - For a potential popup of the archive version: having the last
>   changelog stanza, and/or something like `who-uploads $pkg' would be
>   nice.
> - And, for the version in git, the number of patches and a link.
>
>
Thank you for the feedback, I will update the desgin with the suggestions.


>
> Keep up the good work :)
>
>
Sure, I will :)

Cheers,
> gregor
>
> --
>  .''`.  https://info.comodo.priv.at -- Debian Developer
> https://www.debian.org
>  : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649
> AA06
>  `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation
> Europe
>`-   NP: Kurt Ostbahn & Die Kombo: Wos haasst do Sperrstund?
>
> -BEGIN PGP SIGNATURE-
>
> iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlrJDp9fFIAALgAo
> aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
> RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
> qgbFow/+KLR0VsmzedwzthBEf2JKU1knhfTIYuWl3awJhupVEWQ4OP2yXkZCmQpd
> LFfiKhWUDstLeplZ37F55SYQXPzrZlWIrCXeTddtHRtWOPxvhPQ1q8cP9jaINumH
> aWa5I9xjP98HG7yAtjQ7RbGtKdOn5g4Y8HqWNxt4C+Rd8exMlhlJOngu+0OAc6K9
> 8xvdPZ5+rpsmmMdl/yLpE8QFnzVZNMgkDbLtmh9ZZ0fCqrRJ4YUClqSqUb2rFcqy
> G6otmesVqNBGEmOApvgdKeI7VdbxjpGTy2t4iBSO1D9IlLVssHNmbjIrqZWacRYG
> sXAxWxZuPI8xpFRonc8rZWK2QGQBtVImTuaD43PlJlEKm0+Ne3X2Ph2eANEWImAl
> aX+cNimVAEHBn3g4SU6fkuF93iYXhM2pfTHE4RFl1lg+bnccqBxefrT/q6QkC/CP
> Kh5Riubu1VjAtuaFOHvBa5UzieM3S7xYXVKzuZyizRIqciMkd2uUHKFmon39Zy+A
> RRM5i0gUu/7vGXgU3z12jeZEcLddOxzN8LEx7v70emva21rib9iUk361U/DU7/er
> 8zaEitZtxqZ2tcuuyY8LEkoGVovr16+iz0ZEXTUo08KG3l0BgFtw7fZz27h3UAlK
> lCHuRYXrkcT8Gxmo0+qgBgkkB60XGdgyyg2ln89ziWP/D5VuBD8=
> =tAxA
> -END PGP SIGNATURE-
>
>


Re: Feedback on Package overview page - Distro tracker

2018-04-07 Thread gregor herrmann
On Wed, 04 Apr 2018 18:08:21 +0530, Chirath R wrote:

> Advanced view: https://chirath02.github.io/advance.html
> Simple view: https://chirath02.github.io/index.html
> It would be nice if I could get feedback on the new mockup.

Thanks, and sorry for the late reply.

https://chirath02.github.io/advance.html looks quite nice already.
Some thoughts for potentail further improvements:

- I'd really love to see the version of the package in git; maybe it
  could be shown instead of the literal "Git"? And having the (then)
  three columns with versions next to each other would be nice as
  well.
- Not sure if the "QA" label / link to vcswatch is that helpful, but
  it doesn't really bother me either.
- The various popups are really helpful IMO.
- The "status" in the Git popup is nice; maybe it's possible to also
  add the trailer line of the top changelog entry?
- For a potential popup of the archive version: having the last
  changelog stanza, and/or something like `who-uploads $pkg' would be
  nice.
- And, for the version in git, the number of patches and a link.  


Keep up the good work :)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Kurt Ostbahn & Die Kombo: Wos haasst do Sperrstund?


signature.asc
Description: Digital Signature


Re: Feedback on Package overview page - Distro tracker

2018-04-04 Thread Chirath R
Thank you all for the feedback,

Advanced view: https://chirath02.github.io/advance.html
Simple view: https://chirath02.github.io/index.html

It would be nice if I could get feedback on the new mockup.


Re: Feedback on Package overview page - Distro tracker

2018-03-29 Thread Raphael Hertzog
On Wed, 28 Mar 2018, Chirath R wrote:
> > - the action items should be easily accessible at least in the expanded
> >   view, the number of action items by severity would thus be interesting
> 
> Can I know what an action item here represents. Is it something like a
> `Newer upstream version`?

Everything that can appear in the "action neede" block on the package
page.

> > - the status wrt what's in the VCS
> 
> Status of VCS, as in commits ahead of release version?

Yeah, difference of version compared to the archive, whether the
changelog is marked as UNRELEASED, etc.

> > - the grouping by "status/action needed" makes it easy to find a package
> >   with a specific issue to fix and offers a sort of "process pipeline"
> >   where the package progresses from group to group until's ready for
> >   upload
> 
> It would be nice to highlight packages that are added to a grouping
> recently(maybe after last visit). What do you think?

Maybe. Some sort of "last updated" field is definitely a good idea.

> Depending on whether the logged in user is a part of the team we can show
> two different views and add a toggle button just in case if the user wants
> to see the other information as well.

Yeah, possibly.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/



Re: Feedback on Package overview page - Distro tracker

2018-03-28 Thread Chirath R
>
> Yeah, a PET successor arriving! Thanks for your work on this.
>

You are welcome and thank you for the suggestions :)


> Right.
>
> So what I like about PET and what I'd like to see kept (this also
> answers the question about which fields/information):
>
> - in general the focus on the VCS
> - the separation into sections by categories of _what_ needs to be
>   done: upload from VCS, fix RC bugs, import new upstream releases,
>   ...
> - for each package a clear view of the versions
>   in the VCS, in the archive (in all suites), and upstream
> - anomalies like missing tags
>
> Lucas posted a link to a PET3 instance above. I've now undusted my
> personal instance of the original PET (the one before PET2 and PET3):
> https://www.toastfreeware.priv.at/cgi-bin/pet.cgi

This show some more features than the current incarnation (please
> ignore the design and the completely outdated data).
> I made/make heavy use in PET(3) of all the hover items: the trailer
> of the changelog of the last upload (with links to the full changelog
> in a popup), the links to the bugs (in Debian and upstream, if
> forwarded), in the old PET also the patches or the indicators for
> wrong Maintainer/Uploaders fields. And also, although it's
> not very coherent, the background coloruing and/or hovers that
> indicate _why_ a package is in a given section.
>

This looks awesome, shows a lot of information in a single page and the
more button shows all the information about a package in one single popover.
Thanks for sharing :)

I guess the difficult part (apart from getting VCS information in
> real-time) is to make a layout which includes lots of information
> just one click or hover away and still showing the key facts (the
> main TODO for this package) at first glance.
>

Yes, I would do my best to include everthing at first glance.

---
Thank you,


Re: Feedback on Package overview page - Distro tracker

2018-03-28 Thread Chirath R
>
> Initially, my idea was to implement this team contributor view, similar
> to PET [1]. Mainly, because PET is not so easy to evolve and with the
> migration of git repos to salsa it is not working anymore.


Okay, first we could implement the team contributor view, similar to PET
and them improve on it.


> > As an outsider, I want to check what packages are maintained by the team,
> > the versions availables and what all those packages are about and why
> they
> > are there.
> > - the grouping should be gone, or should be by team-specific categories
> >   which are meaningful for the end user
> > - all the version data is interesting
> > - we want the description too
> > - etc
> >
> > It's not clear that both use cases can be met with a single version of
> the
> > page.
>
> This is a good point, but probably we should accomplish it with another
> page. What do you think?


Yes that would be a good idea, or we could add a toogle to switch between
both the views(It will involve JS).

Thank you for the feedback :)


Re: Feedback on Package overview page - Distro tracker

2018-03-28 Thread Chirath R
Hi Raphael,

Thank you for the detailed feedback.


> I find the table layout more useful.


Yes, table layout works better :)


> As a team contributor, I want to check what packages need to be worked on.
> In this situation you want all relevant informations of the work to be
> done:
> - the action items should be easily accessible at least in the expanded
>   view, the number of action items by severity would thus be interesting
>

Can I know what an action item here represents. Is it something like a
`Newer upstream version`?


> - the bugs data
> - the lintian data
> - the availability of a new upstream release
> - the status wrt what's in the VCS
>

Status of VCS, as in commits ahead of release version?


> - the grouping by "status/action needed" makes it easy to find a package
>   with a specific issue to fix and offers a sort of "process pipeline"
>   where the package progresses from group to group until's ready for
>   upload


It would be nice to highlight packages that are added to a grouping
recently(maybe after last visit). What do you think?


> As an outsider, I want to check what packages are maintained by the team,
> the versions availables and what all those packages are about and why they
> are there.
> - the grouping should be gone, or should be by team-specific categories
>   which are meaningful for the end user
> - all the version data is interesting
> - we want the description too
> - etc
>

I can use tooltips and bootstrap pop overs to display some of this data.


> It's not clear that both use cases can be met with a single version of the
> page.
>

Depending on whether the logged in user is a part of the team we can show
two different views and add a toggle button just in case if the user wants
to see the other information as well.


Re: Feedback on Package overview page - Distro tracker

2018-03-27 Thread gregor herrmann
On Tue, 27 Mar 2018 09:21:25 -0300, Lucas Kanashiro wrote:

> On 03/27/2018 09:09 AM, Raphael Hertzog wrote:
> > On Tue, 27 Mar 2018, Chirath R wrote:
> >> I have made mockup designs for package overview page as part of GSoC
> >> project. It would be nice to get feedback on the design and if you could
> >> mention which fields are most important.

Yeah, a PET successor arriving! Thanks for your work on this.

> > I find the table layout more useful. Concerning the fields, you need
> > to consider the use-cases. Here are the two main use cases that I can
> > imagine:
> Agreed.

+1
 
> > As a team contributor, I want to check what packages need to be worked on.
> > In this situation you want all relevant informations of the work to be
> > done:
> > - the action items should be easily accessible at least in the expanded
> >   view, the number of action items by severity would thus be interesting
> > - the bugs data
> > - the lintian data
> > - the availability of a new upstream release
> > - the status wrt what's in the VCS
> > - the grouping by "status/action needed" makes it easy to find a package
> >   with a specific issue to fix and offers a sort of "process pipeline"
> >   where the package progresses from group to group until's ready for
> >   upload
> Initially, my idea was to implement this team contributor view, similar
> to PET [1]. Mainly, because PET is not so easy to evolve and with the
> migration of git repos to salsa it is not working anymore.
> [1] https://pet.debian.net/pkg-ruby-extras/pet.cgi

Right.

So what I like about PET and what I'd like to see kept (this also
answers the question about which fields/information):

- in general the focus on the VCS
- the separation into sections by categories of _what_ needs to be
  done: upload from VCS, fix RC bugs, import new upstream releases,
  ...
- for each package a clear view of the versions
  in the VCS, in the archive (in all suites), and upstream
- anomalies like missing tags

Lucas posted a link to a PET3 instance above. I've now undusted my
personal instance of the original PET (the one before PET2 and PET3):
https://www.toastfreeware.priv.at/cgi-bin/pet.cgi

This show some more features than the current incarnation (please
ignore the design and the completely outdated data).
I made/make heavy use in PET(3) of all the hover items: the trailer
of the changelog of the last upload (with links to the full changelog
in a popup), the links to the bugs (in Debian and upstream, if
forwarded), in the old PET also the patches or the indicators for
wrong Maintainer/Uploaders fields. And also, although it's
not very coherent, the background coloruing and/or hovers that
indicate _why_ a package is in a given section.

I guess the difficult part (apart from getting VCS information in
real-time) is to make a layout which includes lots of information
just one click or hover away and still showing the key facts (the
main TODO for this package) at first glance.

I think https://chirath02.github.io/tables.html is a good start here.
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: U2: Peace On Earth


signature.asc
Description: Digital Signature


Re: Feedback on Package overview page - Distro tracker

2018-03-27 Thread Lucas Kanashiro
Hello all,


On 03/27/2018 09:09 AM, Raphael Hertzog wrote:
> Hi,
>
> On Tue, 27 Mar 2018, Chirath R wrote:
>> I have made mockup designs for package overview page as part of GSoC
>> project. It would be nice to get feedback on the design and if you could
>> mention which fields are most important.
> I find the table layout more useful. Concerning the fields, you need
> to consider the use-cases. Here are the two main use cases that I can
> imagine:

Agreed.

>
> As a team contributor, I want to check what packages need to be worked on.
> In this situation you want all relevant informations of the work to be
> done:
> - the action items should be easily accessible at least in the expanded
>   view, the number of action items by severity would thus be interesting
> - the bugs data
> - the lintian data
> - the availability of a new upstream release
> - the status wrt what's in the VCS
> - the grouping by "status/action needed" makes it easy to find a package
>   with a specific issue to fix and offers a sort of "process pipeline"
>   where the package progresses from group to group until's ready for
>   upload

Initially, my idea was to implement this team contributor view, similar
to PET [1]. Mainly, because PET is not so easy to evolve and with the
migration of git repos to salsa it is not working anymore.

> As an outsider, I want to check what packages are maintained by the team,
> the versions availables and what all those packages are about and why they
> are there.
> - the grouping should be gone, or should be by team-specific categories
>   which are meaningful for the end user
> - all the version data is interesting
> - we want the description too
> - etc
>
> It's not clear that both use cases can be met with a single version of the
> page.

This is a good point, but probably we should accomplish it with another
page. What do you think?

[1] https://pet.debian.net/pkg-ruby-extras/pet.cgi


Thanks for the feedback :)

Cheers.
Lucas Kanashiro.



signature.asc
Description: OpenPGP digital signature


Re: Feedback on Package overview page - Distro tracker

2018-03-27 Thread Raphael Hertzog
Hi,

On Tue, 27 Mar 2018, Chirath R wrote:
> I have made mockup designs for package overview page as part of GSoC
> project. It would be nice to get feedback on the design and if you could
> mention which fields are most important.

I find the table layout more useful. Concerning the fields, you need
to consider the use-cases. Here are the two main use cases that I can
imagine:

As a team contributor, I want to check what packages need to be worked on.
In this situation you want all relevant informations of the work to be
done:
- the action items should be easily accessible at least in the expanded
  view, the number of action items by severity would thus be interesting
- the bugs data
- the lintian data
- the availability of a new upstream release
- the status wrt what's in the VCS
- the grouping by "status/action needed" makes it easy to find a package
  with a specific issue to fix and offers a sort of "process pipeline"
  where the package progresses from group to group until's ready for
  upload

As an outsider, I want to check what packages are maintained by the team,
the versions availables and what all those packages are about and why they
are there.
- the grouping should be gone, or should be by team-specific categories
  which are meaningful for the end user
- all the version data is interesting
- we want the description too
- etc

It's not clear that both use cases can be met with a single version of the
page.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/