Is there a privacy policy for Cygwin? My company's IT dept needs it before I can install Cygwin on my machine and I can't find one anywhere. Does Cygwin collect information and give it to the developers or a third party? Is there an official doc I can point to that states it definitively?
There is no collection of data of any type from Cygwin.
Paragraph #1 of
https://cygwin.com/faq.html#faq.about
clarifies the project scope.
All the source code is provided as mentioned on
https://cygwin.com/licensing.html
You can also ask the same on the cygwin mailing list
https://cygwin.com/lists.html
Related
For contributing to the github repository i.e. making a PR in the Azure sentinel Reposiroty: https://github.com/Azure/Azure-Sentinel is it necessary to become a Microsoft partner or I can directly contribute without doing so?
The README of that repository contains a contributing section:
Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode#microsoft.com with any additional questions or comments.
For information on how to contribute, refer to the "how to contribute" guide on the project's wiki.
It is not necessary to be a Microsoft partner to contribute. You simply need to accept Microsoft's CLA (Contributor License Agreement). Send a PR and follow the instructions of the bot there, it will tell you how to proceed.
I want To Ask About The licence for ErpNext ERP GNU GPL3 , is it possible to get source code and change it and resell it
I think what you are talking about here is illeagal under theft of intellectual property, if the source code is not listed as "public domain" code odds are it belongs to someone
Does anyone here know what could cause a new feature to not show up in the SharePoint UI?
The solution it is part of has been correctly deployed to the GAC and shows up in the central administration list of deployed farm solutions, the feature appears in the FEATURES folder of the 14 hive, yet the feature itself does not appear in the features list for the site collection, either in the UI or in PowerShell using Get-SPFeature.
Yes, the feature is correctly scoped, and no, it is not hidden. :)
Any thoughts or pointers would be very welcome!
Answer supplied on sharepoint.stackexchange.com, with thanks to Simon Doy. https://sharepoint.stackexchange.com/questions/73871/sharepoint-2010-feature-not-appearing-in-ui
Somehow, something had gone wrong with the installation of the feature, and neither the UI nor commands like Get-SPFeature revealed its existence, although the Install-SPFeature -ScanForFeatures command emboldened below displayed the missing feature.
"Check that the feature has been installed. For example, if you are
performing Update-SPSolution and a new feature has been added between
solution deployments then the feature is not installed by default.
To check do the following:-
Run SharePoint 2010 Management Shell from one of the SharePoint
servers Type Install-SPFeature -ScanForFeatures This will show you any
features that are available in the SharePoint Root but have not been
installed. You can install any missing features using the command :-
Install-SPFeature -AllExistingFeatures
See the following TechNet
Article for more information.
http://technet.microsoft.com/en-us/library/ff607825(v=office.14).aspx"
Look in central admin to see what site collection the feature is deployed to. Make sure in that site collection the feature is turned on.
Also, check the deploy job status to see if it actually finished.
Is there a on install event receiver? If it errors out, the feature will not finish installing even after the DLL is copied.
This question already has answers here:
Developer Documentation: Sharepoint Document Management vs. ScrewTurn Wiki [closed]
(11 answers)
Closed 7 years ago.
Duplicate
Developer Documentation: Sharepoint Document Management vs. ScrewTurn Wiki
I have been tasked with picking a wiki tool for a development organization, comprised of several different development teams. Sharepoint is installed and upper management would prefer this to be used, but in the past it has only used when PMs are forced to use it. None of the developers will update it with content that needs to be shared. I developed in Sharepoint and I liked it, so I have nothing against it. But for this to work I need something I can get everyone using, so Sharepoint will not work.
Step one is to convince management why Sharepoint will not work. We need the typical wiki features:
WYSIWYG, Clean interface, Easy to use, Attach Files to pages, Support for groups of users, Open source, Hosted Locally. (Maybe others I am not considering now?)
Can anyone provide a list of objective reasons why Sharepoint is not the solution we can use to take our first step?
There are many such products out there so step 2 should be easier.
SharePoint is the exact opposite of a wiki: A wiki is lightweight, easy to use, obvious, quick, doesn't get in the way.
To elaborate: A wiki allows your to jot down an idea quickly and moving details to the next page. In SP, people start to create processes, editing rights, workflows.
Wikis are designed to not get in the way. SP is designed to prevent you from doing "something bad"; whatever that might be. Wikis are driven by the idea that brainstorming works in open space while SP is driven by FUD: Who can see this information? Can it be used against me? How can I prevent someone to see/edit something?
Note: This is not a critique of SP per se; it's just how it used in most organizations. If you look at the security settings and edit rights, you sometimes feel like the workers of the company must all have been inmates in some high-profile prison (or should be).
I have absolutely no sharepoint-foo at all, but the sharepoint setup by IT at my employer has a wiki that we can use for documentation. Wouldn't that be good enough? Works ok-ish in firefox on mac, so I'm a happy camper.
SharePoint is best when using many of it's features (eg DM, WCM, workflow, collaberation etc) - you get a lot of it's benefits from the synergy of using all these things together with a common interface.
In any one area though, it's far from the 'best of breed' application - so, if you want a product for a specific job (eg a wiki), SharePoint isn't the most fully-featured/easy-to-use/delete-as-applicable product to be using - there will be products that do that (single) job far better.
You could also try looking at this question to see others experiences with SharePoint wiki's
I have used MediaWiki, Instiki and Sharepoint. Sharepoint does not work correctly with firefox on purpose. Its wiki functionality is an after thought. All kinds of additional features nobody use. But it does appeal to managers.
Instiki can be up and running in less than a minute and MediaWiki has everything you could need. Sharepoint annoyed most people on our team so nobody wanted to use it which meant a lot of knowledge was lost.
Which version of SharePoint are you using WSS 3.0/MOSS 2007 includes both wiki and blog functionality.
Although the SharePoint wiki isn't as feature-rich as most, the fact is that if your developers would not update a SharePoint wiki, chances are that they would not update any other kind, either.
I recommend creating a SharePoint wiki, and then actually reading the starting page, where it gives the definition of wikiwiki. I recommend only using a wiki (of any kind) for documents that can be written quickly, so that developers can get back to developing as soon as possible. Let the structure and accuracy grow over time. Just get the facts into the wiki quickly.
Wikis offer workflows, Document management and more too. I would disagree with those who say you can't do this in a wiki. Check out Confluence by Atlassian
Is there any sort of "out of the box" system within SharePoint (i.e. MOSS 2007) that is useful for tracking/managing permissions. We've got a relatively small installation, but I can easily see special permissions for special users/sites getting out of hand. I'm hoping there's something pre-baked into SharePoint that will help with this, but if there is, I don't know where.
If this isn't available from SharePoint, are there any 3rd party tools people would recommend?
If anyone is curious, I ended up using SharePoint SUSHI for this. It has some useful "security reports" that met my needs. There's a few other goodies included as well. The best part of it all is that it's FREE. :-)
Unfortunately, I haven't found anything that great out of the box in SharePoint for managing or tracking user permissions. You always have an opportunity for customizations. There are some third party tools, however. The best tool I've found for simple management of SharePoint is the Universal SharePoint Manager v2007.
This app has some stellar tools for analyzing security and information about permissions.
Here's a link directly to the feature that might interest you the most: http://www.idevfactory.com/products/uspm2007/features/sharepoint%20user%20site%20security%20analyzer.aspx
I haven't used the USPM myself. I have used the SWAT tool which has a subset of features. iDevFactory does do a good job with their apps and I've found that it's fairly decent ant getting what you want.
Good luck!
Here is a free option that is getting good reviews http://www.codeplex.com/AccessChecker
The SharePoint Administration Toolkit contains a permission tool that shows the effective permissions for a user or group. Becky Bertram has a blog post about this.
See information for downloading it on the SharePoint Team Blog.