Jump to content

Wikipedia talk:Write the article first

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Sagun Kant Aryal (talk | contribs) at 07:28, 12 June 2023 (Biz Serve IT Pvt. Ltd.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

WikiProject iconWikipedia essays Mid‑impact
WikiProject iconThis page is within the scope of WikiProject Wikipedia essays, a collaborative effort to organize and monitor the impact of Wikipedia essays. If you would like to participate, please visit the project page, where you can join the discussion. For a listing of essays see the essay directory.
MidThis page has been rated as Mid-impact on the project's impact scale.
Note icon
The above rating was automatically assessed using data on pageviews, watchers, and incoming links.

Disagree

If the world was my playground and I ruled it, I would see to it that you could not create any article without any article namespace redlinks leading to it. I don't think that would make an existing problem (the adding of unencyclopedic links to existing articles) worse, but it would definitely help resolve two other important problems: the creating of most speedyable articles (some recently deleted articles for example: Curtly morris, Samir faruki, Whiteheads RFC), and the creation of walled gardens. Plrk (talk) 11:14, 15 May 2008 (UTC)[reply]

This guideline, as it reads at this moment anyway, only prohibits redlinks in "list pages, disambiguation pages, or templates," not other articles. I'm not certain, but it seems to me the process championed here would be something like
  1. Redlink the article in related regular articles
  2. Write the article (probably more or less simultaneously with the above)
  3. Leave it a while, for editorial back-and-forth (which no doubt will include notability discussions, among others)
  4. If it survives (as, no doubt, edited and expanded), then it's fair to add it to "lists pages, disambiguation pages, or templates."

Am I on the right track, here? Jackrepenning (talk) 19:24, 21 January 2010 (UTC)[reply]

I disagree too, while it would be nice to have everything n the entrie world listed as articles, it often isn't the case. What this PoV suggests is to restrict lists to only those wikipedia recognises - which I think is the wrong approach. It means that lists of useful information becomes censored. Sure, an author should write a small article about the item in question, but practically that doesn;t happen - and the whole approach of wikipedia is that someone *will* do it.

So, crippling information because you see some redline links is not a good enough reason to follow this advice. Gbjbaanb (talk) 21:55, 27 May 2010 (UTC)[reply]

I want to add my voice to those disagreeing with this essay. Red-links are incredibly useful. The fact they are a different colour makes it clear to the reader that there is something different about them. For editors they're a very useful way of finding articles that need to be created. But crucially, they bridge the gap between reader and editor. It was clicking on red links and seeing "Wikipedia doesn't have an article on this, perhaps you'd like to create it" that drew me in to helping with the project. The same is true for many established and longstanding editors. With the numbers active editors and administrators on the decline, recruitment tools like this are precisely what we need to encourage. WaggersTALK 12:21, 8 April 2021 (UTC)[reply]

WTAF² : Qualifying when this is appropriate

A list of counterexamples would be helpful. There are definitely useful lists that have been made less useful by the overzealous use of this principle. The programming languages example above is one (some software lists w/ commercial entries may be prone to spam by startups; lists about languages themselves, which in compilation are often interesting in the long tail as examples of new ideas or directions, much less so). Another is tables that offer extensive context, where inclusion in the table comes with a statistical summary of impact and relevance.

In all of these cases, removal from a list because the entry obviously fails notability and would be speedied on those grounds, seems reasonable -- removal because noone has successfully created an article that survived merging and deletion over time, even if it is specifically relevant in the context of the list is a much stronger and more volatile filter, and seems unhelpful to me.

As noted above, new page creation has become much more onerous, and stub deletion more common, since this essay was first drafted. So not only does one have to WTAF, any temporary deletion of an article (for needing improvement, lacking sufficient sources, or merging with other articles) can lead to a cascade of deletion of references to it in every associated list. Which is a detriment, not a complement, to human knowledge. – SJ + 21:18, 4 July 2021 (UTC)[reply]

@Sj Most of the templates inside Category:Diplomatic missions by sending country templates not only have structured red links, but also Help:Interlanguage links ~ Shushugah (he/him • talk) 23:10, 8 September 2021 (UTC)[reply]
I would love clarity on whether including redirects (to sections of another article) qualify or not. I know that previews aren't as nice with redirects, but sometimes a section redirect is better than nothing. For example Foxconn union inside Template:Foxconn ~ Shushugah (he/him • talk) 23:10, 8 September 2021 (UTC)[reply]
Thanks! That's a great example; redirects should definitely count. (Often a good and notable concept is redirected to a section for compactness; one certainly shouldn't have to break out a tiny and less-readable stub just to include the section in appropriate lists or tables. – SJ + 22:40, 13 September 2021 (UTC)[reply]
Pinging because this is 2nd time WP:WTAF has been invoked for Help:Interlanguage links. Pinging User:Jax 0677. I would propose adding Help:Interlanguage links as an example of a non pure red-link, because it provides info to existing articles, albeit not in English Wikipedia. ~ 🦝 Shushugah (he/him • talk) 12:56, 9 January 2023 (UTC)[reply]

Biz Serve IT Pvt. Ltd.

Biz Serve IT Pvt. Ltd. (BSIT) is a cybersecurity company based in Nepal. It was established in 2013 and is registered under the Companies Act of Nepal. BSIT is an ISO 27001:2013 ISMS-certified company, demonstrating its commitment to maintaining the highest standards in information security management systems. Sagun Kant Aryal (talk) 06:34, 12 June 2023 (UTC)[reply]

Overview:

BSIT specializes in providing comprehensive cybersecurity services to help organizations understand and protect against cybersecurity risks. Their range of services includes information systems audit, vulnerability assessment, penetration testing, application security testing, security awareness training, and SWIFT CSP assessment. With a diverse range of practice areas and a team of highly trained and certified IT consultants, Biz Serve IT is uniquely qualified to deliver high-value solutions that have a real business impact for its clients.

Accreditations and Partnerships:

BSIT is recognized and listed by the Nepal Telecommunication Authority (NTA) to conduct information system audits for licensed organizations under NTA. Additionally, most of their resources are listed as Information System Auditors by the Institute of Chartered Accountants of Nepal (ICAN).

BSIT is also listed as an independent CSP Assessment provider in the directory published by SWIFT, a global provider of secure financial messaging services. This partnership demonstrates their expertise in conducting SWIFT CSP Independent Assessments for security review and assessment.

Furthermore, BSIT is a subsidiary company of Reanda Biz Serve Pvt. Ltd., which is a licensed firm of Reanda International. Reanda International is an international network of independent accounting and consulting firms and one of Asia's leading global networks.

Vision and Mission:

The vision of Biz Serve IT is to become the most trusted and referred brand in cybersecurity, delivering services of the highest standards. They aim to achieve this by being the partner of choice for clients, providing world-class cybersecurity services based on strong client relationships built on integrity and respect.

Approach and Core Values:

BSIT follows a standard approach and methodology to ensure the highest level of client satisfaction. Their approach includes leveraging the experience of successfully delivered projects, maintaining competency, professionalism, excellence, integrity, and a client-centric approach. They bring tools and templates from previous assignments to accelerate projects, create flexible program plans aligned with client milestones, form teams with deep experience in the related field, and collaborate with clients to understand their needs and priorities.

Services:

BSIT offers a range of specialized cybersecurity services, including:

Information Systems Audit (IS Audit): Conducting audits to identify weaknesses and security gaps within IT infrastructure, helping clients comply with regulatory provisions, standards, policies, and best practices. They provide recommendations to establish effective security programs based on audit findings.

Vulnerability Assessment & Penetration Testing (VAPT): Identifying network and security vulnerabilities, potential exploits, and conducting penetration tests to ensure systems remain updated and protected. They also perform simulated phishing and social engineering assessments to evaluate security awareness and preparedness.

SWIFT CSP Assessment: Conducting independent assessments for security review and assessment of controls mentioned in the CSCF framework v2022. BSIT is a listed SWIFT CSP Independent Assessor for various regions, including Asia Pacific, Africa, North America, South America, Europe, and the Middle East.

IT Policy and Strategy Formulation: Assisting clients in developing IT strategies and policies aligned with their business objectives. This involves evaluating existing policies, studying industry best practices and regulatory requirements, and developing and deploying comprehensive IT policies, standards, guidelines, and operating procedures.

IT Risk Assessment: Identifying IT risks using qualitative or quantitative techniques, gathering information to determine threats and vulnerabilities, assessing the probability and impact of those threats, identifying mitigating controls, and designing audit procedures to test their effectiveness.

MBSS (Minimum Baseline Security Standards)/System Hardening: BSIT assists clients in designing and implementing system hardening documents based on frameworks such as PCI DSS, CIS, and ISO 27001. The goal is to reduce vulnerabilities in an organization's technology infrastructure, including applications, systems, servers, networks, devices, firmware, and other areas. By eliminating potential attack vectors, the system hardening process enhances overall security.

ISO 27001:2013 Implementation: BSIT's team of experts supports clients in implementing ISO 27001:2013, including conducting GAP assessments and providing mitigation strategies according to the ISO 27001 framework.

Team

BSIT boasts a strong team of business professionals and cybersecurity experts. The team consists of qualified and experienced professionals, including offensive and defensive cyber security practitioners, senior chartered accountants, management practitioners, engineers, and auditors. The team holds various certifications, such as CISSP, CISM, CISA, ISO 27001 Lead Auditor, CEH, ISA, CPTE, CPISI, Microsoft Certified Professional, and more. With their expertise, BSIT serves a wide range of clients, including commercial banks, regulatory bodies, telecom companies, software development companies, insurance companies, government entities, and other institutions.