tags: tracking

Action executed in 0.000

Each Tag

tracking

Common tags - number of posts

terms (2), Virginia (2), bills (2), changes (2), terms of service (2), law (2), legislature (2), social media (1), github (1), management (1), integration (1), cycling (1), usage (1), report (1), Nagios (1), Debian (1), fitness (1), OSM (1), ethics (1), routes (1), monitor (1), privacy (1), issue (1), project (1), bug (1), block (1), online (1),

2 way join

bills, tracking, changes, tracking, law, tracking, legislature, tracking, terms, tracking, terms of service, tracking, Virginia, tracking

3 way join

bills, law, tracking, bills, legislature, tracking, Virginia, bills, tracking, changes, terms, tracking, changes, terms of service, tracking, law, legislature, tracking, Virginia, law, tracking, Virginia, legislature, tracking, terms, terms of service, tracking

4 way join

bills, law, legislature, tracking, Virginia, bills, law, tracking, Virginia, bills, legislature, tracking, changes, terms, terms of service, tracking, Virginia, law, legislature, tracking

5 way join

Virginia, bills, law, legislature, tracking

●●●●●○○○

The Virginia Public Access Project

General Assembly Bills The nonprofit Virginia Public Access Project connects Virginians to nonpartisan information about Virginia politics in easily understood ways. VPAP was founded in 1997 on one simple premise: Because Virginia's ethics laws rely on disclosure, it is imperative that citizens have easy access to public documents related to money in politics. VPAP is fiercely nonpartisan. It has no dog in any political fight. Its singular focus is to give Virginians the information...

url: http://www.vpap.org/

type: unknown, format: page

●●●●●○○○

Legislative Information System > 2017 Session

Developed and maintained by the Division of Legislative Automated Systems.

url: https://lis.virginia.gov/

type: project, format: page

●●●●●○○○

Waffle.io ยท Work Better on GitHub Issues

waffle issue board

You already open source your code, so why not open source your process too? Everyone can see your public Waffle board, so go on and show the world what you're working on. Make it easy for contributors to know what's ready to work on next by adding a Waffle badge to your GitHub README, or embed a throughput graph to highlight recent activity on your project.

url: https://waffle.io/

type: project, format: none

●●●●●○○○

CyclePhilly

CyclePhilly logo sharrow

CyclePhilly is a smartphone app for recording your bicycle trips. Data from the app can be used by regional transportation planners in the Philadelphia area to make Philly a better place to ride.

url: http://www.cyclephilly.org/

type: project, format: page

●●●●●○○○

TOSBack | The Terms-Of-Service Tracker

TOSBack logo

TOSBack is a collaboration between the EFF, the Internet Society, and ToS;DR. Every day, we check the Terms and Policies of many online services to see if any of them have changed. The project is currently in beta as we are working on some improvements to ensure greater reliability and coverage. For now, please double check any results with the website operator before relying on them for important legal or journalistic purposes.

url: https://tosback.org/

type: project, format: page

●●●●●○○○

Docracy Terms of Service and Privacy Policy Tracker - Changes

diff icon

Using Docracy's unique document change analysis, we are now tracking terms of service and privacy policies for hundreds of the world's top sites. See below for summaries of recent changes, or to see the complete terms for any of the sites we track.

We started tracking these policies on January 16th, 2013. Earlier versions of selected policies can be found on EFF's TOSBack and TOSBack2 projects.

url: https://www.docracy.com/tos/changes

type: none, format: page

●●●●●●●○

Online Privacy | Proxy | Disconnect

Disconnect Your personal info should be your own. But today thousands of companies invisibly collect your data on the Internet, including the pages you go to and the searches you do. Often, this personal data is packaged and sold without your permission.

url: https://disconnect.me/

type: company, format: page

●●●●●○○○

traineo | Fitness & Weight Loss Community

traineo logo

Our mission is to create the most effective health and fitness community on the web by combining the latest software technology with sound information and services from the world's leading health and fitness experts.

traineo is the culmination of over six years of development, testing and focus group studies in partnership with leading experts in weight loss, health, sports and fitness.

url: http://www.traineo.com/

type: none, format: none

On providing software feedback

I've been using Nagios at work to monitor services across the network. Yesterday's upgrade failed. After fixing that i had some wishes for Nagios that i wanted to pass on. So my question for everyone is do i as (let's pretend i'm) a beginner speak to Debian where i got the software, or directly to Nagios?

On a philosophical note, i've thought about this a bit. I get my software directly from Debian. And Debian gets it from upstream, say Mozilla. Now as an experienced Debian user, i know which bugs are application bug and which ones are packaging bugs. But does the beginner or novice know this? Should they know this? I don't think so. Keeping it simple for the software user would be having a central location where they can provide feedback on software. And it makes sense that this is the place where the they got the software.

Unfortunately this line of thinking implies more work for packagers, namely reading more submissions, evaluating them, and passing some or most of them upstream. In this light, Debian becomes a virtual user of the upstream software. Debian forwards bugs on behalf of the user to upstream.

I'm curious to know if this sort of forwarding communication is built into the Debian structure. I guess not since software providers have various bug reporting interfaces. It would be cool if there Debian could forward bugs to any Bugzilla repository.