271 karma · joined June 1, 2011
[ my public key: https://keybase.io/guruprasad; my proof: https://keybase.io/guruprasad/sigs/glnJlaNs9j3HhyqW9tinIEf7IudHcOUW7ZaFIvo3Pm4 ]
Disclaimer: I work for Canonical but have nothing to do with the distribution or Ubuntu Pro. And I am not speaking on behalf of the company.
Lineage doesn't ship the proprietary Google Apps. It is up to the users to flash it after flashing Lineage
Fasting is not for everyone!
Here in India, the medicines and tools for a diabetic (particulary IDDM) is still prohibitively expensive for most people who have it. The prices of insulins and testing strips have increased by 10% or so many times in the past couple of years. Things like CGMS, insulin pumps are not affordable even to well-off people like me.
There has always been news of research from various government and government aided organizations towards the development of low cost testing strips (at about Rs. 5 per strip compared to Rs. 17 and above for the existing products) but nothing has come out as a product. What's worse is an unknown healthcare company has acquired the technology from ICMR (Indian Council of Medical Research) a year back and till now their only product is a low cost sanitary napkin. Wouldn't be surprised of the involvement of the big pharma companies in the delay.
All this said, at least India doesn't have an insurance system like in the US which has pushed up the prices repeatedly to help the insurance companies (imho an unwanted middleman in most cases) make more and more money.
I am not very optimistic about the future.
I am firm believer in FOSS and I am very glad with GitLab embracing it as much as possible without affecting their revenues. I have started creating my new repositories on GitLab from this month
If Facebook can (ab)use their monopoly and userbase to trick people into supporting Free Basics, just imagine what they will do when they monopolize access to Internet in India for most of the people? Scary!
Facebook has reportedly spent more than $20 million to advertise, push and lobby for Free Basics. Just imagine if that money was used to provide some MB of unrestricted internet usage to people. A lot of people would have benefited. That also begs the question, how is Facebook going to recoup that? And every answer to that question is bad for those poor users that Facebook is connecting to their own walled garden impersonating internet.
Also if people can afford to get phones that support connecting to internet (these days almost all such phones are smartphones and prices start from Rs. 2000 onwards), can they not afford Rs.100 odd to get a reasonable amount of 2G data to access the actual internet? Imho most of them can.
> Thinking the other way around, what about a browser where features are enabled and then you disable what you do not like? Why is that bad in your opinion? The customize menu that allows you to reorder and remove features is not enough for you?
Not sure if you understood me right. All I stated was that if it had been an extension that shipped with Firefox and turned on by default, it is easier for the user to turn it off or remove it than when it is a part of core Firefox. Please see my above comment for details. I did not talk about browsers with features turned off by default.
"Firefox Input is Mozilla's primary feedback mechanism for products.It is set up to be a method of one-way communication about your experiences in using our products, the Internet you view it through, and what Mozilla can do to make that experience better"
So please provide do provide feedback on various Mozilla products on Mozilla Input and not just limit it to this Pocket integration.
Not sure how it was easier, since there is already a Firefox extension for Pocket which could have been shipped as an extension installed by default (but removable by users who do not want it)
> Instead of offering just a web view, Mozilla is trying to bundle features that the users find useful. None of the said features does you any harm if you don't use them.
A lot of privacy-aware users will expect Mozilla to provide a way to easily disable and remove what are essentially features tangential to the core functionality of the browser. By making it a feature integrated into the core Firefox, the users now have to jump through various hoops to come close to achieving that. Having it as an extension makes it much easier to do so.
Disclaimer: I contribute to Mozilla Input codebase but have no affiliation with Mozilla.
The main assumption in the Integration-Manager workflow is that code from repositories of other users is always pulled by the owner of the current repository as and when appropriate.
So if dev1 and dev2 are working on the same feature in 2 different forks of the main repository, dev1 has to pull commits from dev2 that are needed in his/her fork and dev2 has to do the same in his/her fork. Once the feature is complete, the merge request is created from one of the 2 forks.
Yes it is harder to mention issues, but that can be done in the message of the merge commit. Since forks are essentially equivalent to branches in this workflow, I usually don't mind referring to issues in the individual commits itself which would link to the correct issue on getting merged to the main repository.
We do this with our team's projects hosted on Bitbucket, ymmv.
I have come across these things that you have pointed out and yes they are steps in the right direction. But if you ask me if any of those will become the mainstream de-facto thing that everyone will use some time in the future? Based on the evidence available at the moment, I would still stick to what I said and maintain that it is highly unlikely given the current state of affairs. Yes, I would be very glad to be proven wrong but not enough atm to feel optimism. :)
It would be great to start from scratch and build things without the expectation of any trustability from anyone, but I don't see that happening ever!
Sad to see that the people elected by other people like us to do good for all the people tend to do everything other than that.
We have a team and by default all the members of the team have read access to all the team repositories (unless overridden at a repo level) and write access to the repositories they created or forked. Developers can create forks within the team namespace and send pull requests between themselves and to the official "blessed" repo from which releases are done. Those with write access to some repositories can commit to those repos and also merge pull requests. Admin can basically do everything within the team namespace.
That said, congratulations on keeping GitLab rolling forward with more and more features and bugfixes every release.
Edit: Fixed a typo and added some more detail.
http://ibin.co/1kret3oW7caZ illustrates whitespace wastage in the blog
Edit: Added an illustration
Location: Bangalore, India
Remote: Yes
Willing to relocate: No
Technologies: Debian, Python, Django, C++, SAN Storage, Linux system administration.
Code: GitHub: https://github.com/lgp171188 Bitbucket: https://bitbucket.org/guruprasad
Resume: https://docs.google.com/file/d/0By4tOruhioffYk8ySEdweTZEdWc/...
Email: lgp.171188 at gmail
Remote: Yes
Willing to relocate: No
Technologies: Debian, Python, Django, C++, SAN Storage, Linux system administration.
Code: GitHub: https://github.com/lgp171188 Bitbucket: https://bitbucket.org/guruprasad
Resume: https://docs.google.com/file/d/0By4tOruhioffYk8ySEdweTZEdWc/... Email: lgp.171188 at gmail