| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | MUST-HAVE | NICE-TO-HAVE | Migration MUST-HAVE | Migration NICE-TO-HAVE | PROS | CONS | DEPENDS - TAG | |||||||||||||||||||
2 | Yes | Trac is missing critical feature such as code review and private tickets. The email notifications in trac are horrible with that "cc" concept... But for me, having a way to integrate our personal developer git repository with a code review tool and ticketing would be ideal world. | "Handle tickets","Git (read-only)","Issues","Labels/Tags","Milestones","Code reviews (no write access to git repos)","Private issues (not public)","Possibility to use encrypted lists/email for private issues" | "Handle Wiki","2fa support" | A way to have Labels/Tags *per* project that is "tor" and "tbb" wouldn't share the same list of labels. | "Migrate tickets","Migrate comments (respect tickets history and interactions)","Redirect urls","Respect tickets numbers" | "Migrate wiki pages","Migrate wiki edit and revision history" | |||||||||||||||||||
3 | Yes | Trac is difficult to use, search, slow and doesn't work well on a mobile device. | "Code reviews (no write access to git repos)","Projects flow","Milestones","Labels/Tags","Issues","Git (read-only)","Project management functionalities","Handle tickets" | mobile/responsive interface, email based interaction with tickets | "2fa support","Possibility to use encrypted lists/email for private issues" | integration with end-user support, helpdesk type capabilities | "Migrate tickets","Respect tickets numbers" | "Migrate wiki pages","Migrate comments (respect tickets history)","Redirect urls","Respect tickets numbers" | ||||||||||||||||||
4 | Depends | "Handle tickets" | "Handle Wiki" | "Migrate tickets","Respect tickets numbers" | "Migrate wiki pages" | |||||||||||||||||||||
5 | No | if it ain't broke don't fix it | ||||||||||||||||||||||||
6 | Depends | "Labels/Tags","Issues","Git (read-only)","Milestones","Handle wiki","Handle tickets" | Processes and/or flows should be very, very flexible to accommodate different ways of working. User interface and wiki syntax should be straightforward (small learning curve). (Trac has git plugins.) | "Respect tickets numbers","Redirect urls","Migrate comments (respect tickets history and interactions)","Migrate wiki pages","Migrate tickets" | "Migrate wiki edit and revision history" | |||||||||||||||||||||
7 | Depends | If the new thing had the features of trac and was faster, that sounds fine. If it didn't, then why would we move? I guess I don't care that much =) | "Handle tickets","Handle wiki","Project management functionalities","Issues","Private issues (not public)" | "Git (read-only)","Code reviews (no write access to git repos)","Projects flow","Milestones","2fa support","Possibility to use encrypted lists/email for private issues" | pastebin | "Migrate tickets","Migrate comments (respect tickets history and interactions)","Migrate wiki pages" | "Respect tickets numbers","Redirect urls" | Speed | neutral | |||||||||||||||||
8 | Depends | trac sucks, but migrating it seems like a lot of work! | "Handle tickets","Handle wiki","Project management functionalities" | "2fa support","Issues","Milestones","Projects flow" | "Migrate wiki pages","Redirect urls" | Migration effort | yes | |||||||||||||||||||
9 | No | Trac fulfills my needs. I was around when we migrated *to* trac and doing another migration will be a huge pain. Besides the obvious upfront costs there's also thousands of things that link to it. If you really go this route please consider making a redirector that provides 302s from ticket urls to the ticket's location in the new system. | "Handle tickets","Handle wiki" | I like the Unix philosophy of 'do one thing and do it well'. For instance, you list 'Git (read-only)' up there. Why? We have GitWeb. Tickets and wiki are mandatory. Anything outside of that I'm not really concerned about and suspect could be a different tool. For instance, for code reviews ReviewBoard is a great tool. | "Migrate tickets","Migrate wiki pages","Migrate comments (respect tickets history and interactions)","Redirect urls","Respect tickets numbers","Migrate wiki edit and revision history" | |||||||||||||||||||||
10 | Yes | Compared to github and gitlab, every time I use trac I feel like it slows me down. | "Handle tickets","Handle wiki","Project management functionalities","Git (read-only)","Issues","Labels/Tags","Code reviews (no write access to git repos)","2fa support" | "Possibility to use encrypted lists/email for private issues","Private issues (not public)","Milestones","Projects flow" | Ability to create teams and reply to tickets with email | "Migrate tickets","Migrate comments (respect tickets history and interactions)","Redirect urls","Respect tickets numbers","Migrate wiki pages","Migrate wiki edit and revision history" | ||||||||||||||||||||
11 | Depends | Pros: possibly easier to manage notifications, tickets, and overall work as a volunteer. Cons: may be difficult to migrate all the old tickets with comments attributed correctly (see also the OONI git->trac fiasco of a few years ago). | "Handle tickets","Issues","Labels/Tags","Milestones" | "Private issues (not public)","Possibility to use encrypted lists/email for private issues" | "view file/patch" feature with syntax highlighting would be nice. | "Migrate tickets","Migrate comments (respect tickets history and interactions)","Redirect urls","Respect tickets numbers" | Workflow | Migration effort | yes | |||||||||||||||||
12 | Depends | I've liked trac over the years, but it certain has "problems". However, other things do to, so ... | "Git (read-only)","Issues" | "Project management functionalities","Handle Wiki","Code reviews (no write access to git repos)","2fa support","Possibility to use encrypted lists/email for private issues" | command-line interface, tickets-are-stored-in-git?, ... | "Migrate tickets","Migrate wiki pages","Migrate comments (respect tickets history and interactions)" | "Redirect urls","Respect tickets numbers","Migrate wiki edit and revision history" | |||||||||||||||||||
13 | No | Trac has very important history in it, documenting all of our patches. Unless we can migrate and perfectly preserve this history (including links), I would be very concerned about changing. | "Handle tickets","Handle wiki","Project management functionalities","Issues","Labels/Tags" | Open source, attachments | "Code reviews (no write access to git repos)","Milestones","Projects flow","2fa support","Private issues (not public)" | For me, the biggest problem with Trac is its slowness. Ideally we could t figure out how to speed up the performance. | "Migrate tickets","Migrate wiki pages","Migrate comments (respect tickets history and interactions)","Redirect urls","Respect tickets numbers","Migrate wiki edit and revision history" | |||||||||||||||||||
14 | Trac has very important history in it, documenting all of our patches. Unless we can migrate and perfectly preserve this history (including links), I would be very concerned about changing. | "Handle tickets","Handle wiki","Project management functionalities","Issues","Labels/Tags" | Open source, attachments | "Code reviews (no write access to git repos)","Milestones","Projects flow","2fa support","Private issues (not public)" | For me, the biggest problem with Trac is its slowness. Ideally we could t figure out how to speed up the performance. | "Migrate tickets","Migrate wiki pages","Migrate comments (respect tickets history and interactions)","Redirect urls","Respect tickets numbers","Migrate wiki edit and revision history" | ||||||||||||||||||||
15 | Depends | Trac is mostly functioning well for my needs. Moving away from it without friction (in terms of current URLs breaking, ticket numbers being reassigned, not losing history on bugs etc) seems pretty hard. | "Handle tickets","Issues" | Compatibility with existing links, pseudonymous access (cypherpunks account) | "Project management functionalities","Git (read-only)","Milestones","Labels/Tags","Code reviews (no write access to git repos)","Private issues (not public)" | "Migrate tickets","Migrate comments (respect tickets history and interactions)","Redirect urls","Respect tickets numbers" | "Migrate wiki pages","Migrate wiki edit and revision history" | Migration effort | no | |||||||||||||||||
16 | Yes | Trac generally sucks, but over the past 2 years we've been trying to use trac to do too many things that it's not very good at. I'm specifically thinking about project management things like tags/keywords, task points and various automations. I feel like there must be better tools than trac to do what we want, but I actually have no idea what kind of stacks exist. Also, I don't like how trac looks. | "Handle tickets","Handle wiki","Project management functionalities","Issues","Labels/Tags","Milestones","Projects flow","Code reviews (no write access to git repos)","Private issues (not public)" | Ehm, in the above "requirements" I just ticked the things I care a lot about. I'm not sure if there exists a single software that can handle all the requirements we care about. So I imagine that the "new solution" might be a stack of software that can do what we want better than trac. | "Handle Tickets","Handle Wiki","Git (read-only)","Project management functionalities","Milestones","Issues","Projects flow","Labels/Tags","Code reviews (no write access to git repos)","Private issues (not public)","2fa support","Possibility to use encrypted lists/email for private issues" | "Migrate tickets","Migrate comments (respect tickets history and interactions)" | "Migrate tickets","Migrate wiki pages","Migrate comments (respect tickets history)","Respect tickets numbers","Redirect urls","Migrate wiki edit and revision history" | |||||||||||||||||||
17 | Trac generally sucks, but over the past 2 years we've been trying to use trac to do too many things that it's not very good at. I'm specifically thinking about project management things like tags/keywords, task points and various automations. I feel like there must be better tools than trac to do what we want, but I actually have no idea what kind of stacks exist. Also, I don't like how trac looks. | "Handle tickets","Handle wiki","Project management functionalities","Issues","Labels/Tags","Milestones","Projects flow","Code reviews (no write access to git repos)","Private issues (not public)" | Ehm, in the above "requirements" I just ticked the things I care a lot about. I'm not sure if there exists a single software that can handle all the requirements we care about. So I imagine that the "new solution" might be a stack of software that can do what we want better than trac. | "Handle Tickets","Handle Wiki","Git (read-only)","Project management functionalities","Milestones","Issues","Projects flow","Labels/Tags","Code reviews (no write access to git repos)","Private issues (not public)","2fa support","Possibility to use encrypted lists/email for private issues" | "Migrate tickets","Migrate comments (respect tickets history and interactions)" | "Migrate tickets","Migrate wiki pages","Migrate comments (respect tickets history)","Respect tickets numbers","Redirect urls","Migrate wiki edit and revision history" | yes | |||||||||||||||||||
18 | Yes | I dislike trac from a usability point of view. | cypherpunks' support (anon access). Filter must be at least as powerful as trac's filter. Email support: subscribe/reply to tickets via email. | |||||||||||||||||||||||
19 | Depends | I wouldn't move away from Trac, unless some other alternative has features that we really need that Trac doesn't have, or is much better for us for some reason. I don't know if that's the case. | "Handle tickets","Labels/Tags","Issues" | allowing comments / bug reports from anonymous people without creating an account | "Possibility to use encrypted lists/email for private issues","Private issues (not public)" | being able to view/modify bugs with command line tool, or email | "Migrate comments (respect tickets history and interactions)","Migrate tickets","Redirect urls","Respect tickets numbers" | "Migrate wiki pages","Migrate wiki edit and revision history" | neutral | |||||||||||||||||
20 | Depends | I'd like to replace trac with something more maintainable, but from my POV, the usability problems are ones I've learned to work around. | "Handle tickets","Handle wiki","Issues","Labels/Tags","Code reviews (no write access to git repos)" | "guest" accounts with limited privileges. the ability for users to post issues without providing email addresses. Good privacy for users. Must be fairly secure. Needs data export interface. Needs batch operations on tickets. Also, when I list "must have" requirements above, I don't think these all need to be in the same tool. It's okay to have a wiki that isn't integrated with the bugtracker. | "Git (read-only)","Project management functionalities","Projects flow","Milestones","Private issues (not public)","2fa support","Possibility to use encrypted lists/email for private issues" | "Migrate tickets","Migrate wiki pages","Redirect urls","Migrate comments (respect tickets history and interactions)","Respect tickets numbers" | Usability | yes | ||||||||||||||||||
21 | Depends | It would be great to have more control over subscribing to certain tickets, components, milestones to get updates for. And it would be nice if the web interface were more user-friendly. Oh, an email-to-Trac interface where people can submit tickets or comment on tickets would be great. | "Handle tickets","Issues","Labels/Tags","Milestones" | "Handle Wiki","Project management functionalities","Git (read-only)","Projects flow","Code reviews (no write access to git repos)","Private issues (not public)" | "Migrate tickets","Migrate comments (respect tickets history and interactions)","Respect tickets numbers","Migrate wiki edit and revision history","Migrate wiki pages","Redirect urls" | Workflow | yes | |||||||||||||||||||
22 | Yes | Trac doesn't have any integrations for viewing diffs or doing code review. It also doesn't have a good notification system, tagging/keyword system, the threading is all weird, and the query system is awkward. Essentially, it's just not modern enough and should be put to rest. | "Handle tickets","Project management functionalities","Issues","Labels/Tags","Milestones","Code reviews (no write access to git repos)","Private issues (not public)" | Configurable notification settings, and better query functionality. | "Projects flow","2fa support","Possibility to use encrypted lists/email for private issues" | "Migrate tickets","Migrate comments (respect tickets history and interactions)","Redirect urls" | "Respect tickets numbers" | |||||||||||||||||||
23 | Depends | "Handle tickets","Issues","Milestones","Labels/Tags","Code reviews (no write access to git repos)" | per-developer dashboard showing tickets and their status. all functionality to work without requiring javascript. | "Private issues (not public)","Possibility to use encrypted lists/email for private issues" | "Migrate tickets","Migrate comments (respect tickets history and interactions)","Redirect urls" | "Migrate wiki pages","Migrate wiki edit and revision history" | ||||||||||||||||||||
24 | Depends | "Handle tickets","Git (read-only)","Issues","Labels/Tags","Milestones","Code reviews (no write access to git repos)" | "Handle Tickets","Project management functionalities","Git (read-only)","Issues","Milestones","Labels/Tags","Code reviews (no write access to git repos)","Private issues (not public)","2fa support","Possibility to use encrypted lists/email for private issues" | "Migrate tickets","Migrate comments (respect tickets history and interactions)","Redirect urls" | "Migrate tickets","Migrate comments (respect tickets history)","Redirect urls" | |||||||||||||||||||||
25 | Depends | I don't want to move because I know how the current platform works. I do want to move because it's clunky and takes time to maintain. I don't want to move because of the inevitable loss of information involved. | "Handle tickets","Issues","Labels/Tags","Milestones" | Parent / Child Tickets This is a weird way to ask this question: I would like to have most of these features somewhere, but they don't need to be in the trac replacement. | "Handle Tickets","Handle Wiki","Git (read-only)","Issues","Milestones","Labels/Tags","Code reviews (no write access to git repos)","Private issues (not public)","2fa support","Possibility to use encrypted lists/email for private issues" | I think we could keep trac as our wiki, but we'd lose the integration functionality with ticket numbers, which I use heavily. Guiding new users to assign tickets to the right project. (Automating this process as much as possible.) | "Migrate tickets","Migrate wiki pages","Migrate comments (respect tickets history and interactions)","Respect tickets numbers" | "Migrate tickets","Migrate wiki pages","Migrate comments (respect tickets history)","Redirect urls","Respect tickets numbers","Migrate wiki edit and revision history" | Mainteinance cost, Usability | Information Loss, Migration Effort | neutral | |||||||||||||||
26 | Depends | Trac is okay once you have learned it (not so easy to get started with). I don't like having to solve a captcha every time I add an http link to a wiki page. I don't like getting auto-subscribed to tickets just by commenting on them. | "Handle tickets","Issues","Labels/Tags" | Please please please keep existing links working if at all possible. We already have https://bugs.torproject.org/nnnn permalinks, but many sources (even published research papers) use https://trac.torproject.org/projects/tor/ticket/nnnn. I hope that it will be possible to add redirects to account for those. The other links that matter to me are fragment identifiers for individual comments, e.g. https://bugs.torproject.org/nnnn#comment:10. | "Handle Wiki","Git (read-only)" | It's good if whatever we migrate to also will have the ability to keep URLs unbroken the next time we have to migrate. So something with a sensible URL format is better than something without. It would be nice if it were possible to easily link to a file or commit in a git repository viewer, like GitHub has when you write a commit hash (https://guides.github.com/features/mastering-markdown/#GitHub-flavored-markdown). I think Trac currently has something like this, but it only works for the tor.git repo. Currently what I do is laboriously look up URLs on gitweb.torproject.org and paste them in. Here's an example of commit hashes not being linked: https://bugs.torproject.org/20927#comment:2 Here's an example of how I want to link to specific commits: https://bugs.torproject.org/10935#comment:18 | "Migrate tickets","Migrate comments (respect tickets history and interactions)","Redirect urls","Respect tickets numbers" | "Migrate wiki pages","Migrate wiki edit and revision history" | Usability | yes | ||||||||||||||||
27 | Yes | I actually currently do not use trac for managing the projects I work mainly on, but instead use github, due to the bad usability of trac. One of the main features that trac lacks, that has strongly affected our decision is that the code review process is very well integrated into the ticket management workflow. | "Handle tickets","Handle wiki","Project management functionalities","Code reviews (no write access to git repos)","Git (read-only)" | "Migrate tickets","Migrate wiki pages","Redirect urls" | ||||||||||||||||||||||
28 | No | Trac works well, has all our history, is familiar to new developers since other projects use it... and does everything we need. | "Handle tickets","Handle wiki","Project management functionalities","Git (read-only)","Issues","Labels/Tags","Milestones" | free software, self-hosted, usable anonymously (eg, on trac we have the shared cypherpunks account) | "2fa support","Possibility to use encrypted lists/email for private issues","Code reviews (no write access to git repos)","Private issues (not public)","Projects flow" | "Migrate tickets","Migrate wiki pages","Migrate comments (respect tickets history and interactions)","Redirect urls","Respect tickets numbers","Migrate wiki edit and revision history" | ||||||||||||||||||||
29 | Yes | Trac is not very friendly and not intuitive for new potential contributors. | "Handle tickets","Project management functionalities","Git (read-only)","Issues","Labels/Tags","Milestones","Code reviews (no write access to git repos)","Private issues (not public)" | "2fa support","Projects flow","Possibility to use encrypted lists/email for private issues" | "Migrate tickets","Redirect urls","Migrate comments (respect tickets history and interactions)" | "Migrate wiki edit and revision history" | ||||||||||||||||||||
30 | Depends | "Git (read-only)","Handle tickets" | "Labels/Tags","Code reviews (no write access to git repos)","Handle Wiki" | "Redirect urls","Respect tickets numbers" | ||||||||||||||||||||||
31 | Yes | I dislike trac--it's hard to visualize what's going on organizationally and collaborate. | "Projects flow","Milestones","Issues","Project management functionalities","Handle wiki" | "Handle Tickets","Code reviews (no write access to git repos)" | "Migrate wiki pages","Migrate tickets","Redirect urls" | "Migrate comments (respect tickets history)","Respect tickets numbers" | ||||||||||||||||||||
32 | Depends | Issues, attachments, and metadata may be lost in transition. On the other hand, more functionality and better workflow would make me happy to move. | "Handle tickets","Issues","Labels/Tags","Private issues (not public)" | "Project management functionalities","Git (read-only)","Milestones","Projects flow","2fa support","Handle Wiki" | With respect to project management functionality - it would be really useful to have backlog and current iteration queues, as well as ticket work time estimates and actual time taken. Ideally the tracker would also be able to give us statistics on estimating accuracy and throughput. | "Migrate tickets","Migrate comments (respect tickets history and interactions)","Respect tickets numbers" | "Migrate wiki pages","Redirect urls" | Workflow | Information Loss, Migration Effort | neutral | ||||||||||||||||
33 | No | We've been using it for a while, I don't necessarily see any features that are missing, at least as far as handling tickets for Atlas goes. | "Handle tickets","Handle wiki","Git (read-only)","Milestones" | Please consider that an alternative to Trac, if we must have one, doesn't necessarily have to be an all-in-one solution, and it could be multiple solutions that interoperate (at least to begin with, at some point they'll all stop working together and we'll have some fun). | "Handle Tickets","Handle Wiki","Git (read-only)","Milestones" | "Migrate tickets","Migrate wiki pages","Migrate comments (respect tickets history and interactions)","Redirect urls","Respect tickets numbers" | "Migrate tickets","Migrate wiki pages","Redirect urls","Migrate comments (respect tickets history)","Respect tickets numbers","Migrate wiki edit and revision history" | |||||||||||||||||||
34 | Depends | Replacing Trac is not worthwhile unless we are solving specific problems or gaining important features. | "Handle tickets","Private issues (not public)" | "Code reviews (no write access to git repos)","Possibility to use encrypted lists/email for private issues","2fa support" | Improved usability, e.g., autocompletion for users is terrible currently. | "Migrate tickets","Migrate wiki pages","Migrate comments (respect tickets history and interactions)","Respect tickets numbers" | "Redirect urls","Migrate wiki edit and revision history" | no | ||||||||||||||||||
35 | Depends | Trac is slightly clunky. It'd be nice to replace it but it may not be worth the effort. | "Handle tickets","Labels/Tags" | "Possibility to use encrypted lists/email for private issues","Code reviews (no write access to git repos)" | better UI; completion for login ids is horrible right now. | "Migrate tickets","Migrate comments (respect tickets history and interactions)","Redirect urls" | "Respect tickets numbers" | Information Loss, Migration Effort | neutral | |||||||||||||||||
36 | Yes | Too old, clunky, and non-intuitive. | "Handle tickets","Handle wiki","Issues","Labels/Tags","Milestones" | "Code reviews (no write access to git repos)","Projects flow","Git (read-only)" | "Migrate tickets","Migrate wiki pages","Migrate comments (respect tickets history and interactions)" | "Respect tickets numbers","Redirect urls" | ||||||||||||||||||||
37 | Yes | Trac is unintuitive and hard to find what I'm looking for. Its friction prevents me from contributing as much as I'd like to. | "Handle tickets","Git (read-only)","Project management functionalities","Labels/Tags","Issues","Projects flow","Code reviews (no write access to git repos)","Private issues (not public)" | "Milestones","Projects flow" | "Migrate tickets","Migrate comments (respect tickets history and interactions)" | "Respect tickets numbers","Redirect urls","Migrate wiki pages","Migrate wiki edit and revision history" | ||||||||||||||||||||
38 | Yes | "Handle tickets","Project management functionalities","Git (read-only)","Issues","Labels/Tags","Milestones","Code reviews (no write access to git repos)","Private issues (not public)","2fa support" | "Migrate tickets","Migrate wiki pages","Migrate comments (respect tickets history and interactions)","Respect tickets numbers" | "Redirect urls" | ||||||||||||||||||||||
39 | Depends | "Handle tickets","2fa support","Private issues (not public)","Possibility to use encrypted lists/email for private issues","Labels/Tags" | "Git (read-only)","Handle Wiki","Issues","Code reviews (no write access to git repos)" | "Migrate tickets","Migrate comments (respect tickets history and interactions)","Redirect urls","Respect tickets numbers" | "Migrate wiki pages","Migrate wiki edit and revision history" | |||||||||||||||||||||
40 | Depends | "Milestones","Issues","Handle wiki","Handle tickets","Project management functionalities","Git (read-only)","Labels/Tags","Projects flow","Code reviews (no write access to git repos)" | "Private issues (not public)","Possibility to use encrypted lists/email for private issues" | "Redirect urls","Respect tickets numbers","Migrate wiki edit and revision history","Migrate comments (respect tickets history and interactions)","Migrate wiki pages","Migrate tickets" | ||||||||||||||||||||||
41 | Yes | "Handle tickets","Handle wiki","Project management functionalities","Git (read-only)","Issues","Labels/Tags","Milestones","Projects flow" | "Migrate wiki pages","Migrate tickets","Migrate comments (respect tickets history and interactions)","Redirect urls","Respect tickets numbers","Migrate wiki edit and revision history" | |||||||||||||||||||||||
42 | Depends | "Issues","Handle wiki","Handle tickets","Project management functionalities","Labels/Tags" | "Code reviews (no write access to git repos)","Git (read-only)","Projects flow","Milestones","2fa support" | "Migrate tickets","Migrate wiki pages","Migrate comments (respect tickets history and interactions)","Redirect urls","Respect tickets numbers","Migrate wiki edit and revision history" | ||||||||||||||||||||||
43 | Depends | "Handle tickets","Handle wiki","Project management functionalities","Git (read-only)","Issues","Labels/Tags","Milestones","2fa support" | "Projects flow","Possibility to use encrypted lists/email for private issues" | "Migrate tickets","Migrate wiki pages","Migrate comments (respect tickets history and interactions)","Redirect urls","Respect tickets numbers" | "Migrate wiki edit and revision history" | |||||||||||||||||||||
44 | ||||||||||||||||||||||||||
45 | ||||||||||||||||||||||||||
46 | ||||||||||||||||||||||||||
47 | ||||||||||||||||||||||||||
48 | ||||||||||||||||||||||||||
49 | ||||||||||||||||||||||||||
50 | ||||||||||||||||||||||||||
51 | ||||||||||||||||||||||||||
52 | ||||||||||||||||||||||||||
53 | ||||||||||||||||||||||||||
54 | ||||||||||||||||||||||||||
55 | ||||||||||||||||||||||||||
56 | ||||||||||||||||||||||||||
57 | ||||||||||||||||||||||||||
58 | ||||||||||||||||||||||||||
59 | ||||||||||||||||||||||||||
60 | ||||||||||||||||||||||||||
61 | ||||||||||||||||||||||||||
62 | ||||||||||||||||||||||||||
63 | ||||||||||||||||||||||||||
64 | ||||||||||||||||||||||||||
65 | ||||||||||||||||||||||||||
66 | ||||||||||||||||||||||||||
67 | ||||||||||||||||||||||||||
68 | ||||||||||||||||||||||||||
69 | ||||||||||||||||||||||||||
70 | ||||||||||||||||||||||||||
71 | ||||||||||||||||||||||||||
72 | ||||||||||||||||||||||||||
73 | ||||||||||||||||||||||||||
74 | ||||||||||||||||||||||||||
75 | ||||||||||||||||||||||||||
76 | ||||||||||||||||||||||||||
77 | ||||||||||||||||||||||||||
78 | ||||||||||||||||||||||||||
79 | ||||||||||||||||||||||||||
80 | ||||||||||||||||||||||||||
81 | ||||||||||||||||||||||||||
82 | ||||||||||||||||||||||||||
83 | ||||||||||||||||||||||||||
84 | ||||||||||||||||||||||||||
85 | ||||||||||||||||||||||||||
86 | ||||||||||||||||||||||||||
87 | ||||||||||||||||||||||||||
88 | ||||||||||||||||||||||||||
89 | ||||||||||||||||||||||||||
90 | ||||||||||||||||||||||||||
91 | ||||||||||||||||||||||||||
92 | ||||||||||||||||||||||||||
93 | ||||||||||||||||||||||||||
94 | ||||||||||||||||||||||||||
95 | ||||||||||||||||||||||||||
96 | ||||||||||||||||||||||||||
97 | ||||||||||||||||||||||||||
98 | ||||||||||||||||||||||||||
99 | ||||||||||||||||||||||||||
100 |